[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

RE: Asynchronous message queue by SMTP&POP3

• From: Michael Rossi <mrossi@c...>
• To: xml-dev@x...
• Date: Mon, 7 Feb 2000 13:57:54 -0500

K.Kawaguchi wrote:
> 
> > I would have thought layering a messaging protocol over existing email
> > protocols, would be a bad idea. It would be better to have a service
that
> > could contain proccessing components based on the type of message going
in
> > e.g. the DTD. and also make it secure e.g. SSL from the start. The
service
> 
> Well, you are right in the sense that such a full fledged system is
> necessary.  I agree.
> 
> But at the same time I personally think that SMTP/POP3 can still work
> very well in many situations; especially for lightweight systems.
> Or, is it only me who feel like this?   If so, what am I missing?

   I don't think it's just you. A dedicated system/service could undoubtedly
yield some benefits for an environment with very robust requirements. But it
would also probably mean reinventing a few wheels along the way. I would
think you could meet a large majority of common requirements with an
adequate specification of how common transport protocols should be used.

> Yet unsolved question is whether such a component already exists or
> not...

   I don't know of any components specifically designed to optimize this
environment. The WfMC (http://wfmc.org) did do a MIME binding of their
abstract interoperability spec, which now has an XML syntax binding in beta.
The intent of the original MIME binding was to exchange these messages over
common e-mail protocols. But I don't think they developed any tools to
facilitate the exchange, sorry.

Michael A. Rossi
mailto:mrossi@j...
856-983-4400 x4911

• Follow-Ups:
  • Adequate specification of the interface
    • From: "K.Kawaguchi" <ml@s...>

• Prev by Date: Re: Asynchronous message queue by SMTP&POP3
• Next by Date: Re: SAX2: Interning names in namespaces
• Previous by thread: Moderatorial: Indentification of quotes
• Next by thread: Adequate specification of the interface
• Index(es):
  • Date
  • Thread