[Home] [By Thread] [By Date] [Recent Entries]

  • To: Bill de hÓra <bill.dehora@p...>,"CHIUSANO, Joseph" <JCHIUSANO@l...>,"'Maciejewski, Thomas' " <Thomas.Maciejewski@l...>
  • Subject: RE: ( Slightly off topic ) JMS and other messaging
  • From: "CHIUSANO, Joseph" <JCHIUSANO@l...>
  • Date: Wed, 18 Sep 2002 23:44:30 -0400
  • Cc: <xml-dev@l...>
  • Thread-index: AcJfJfeaFkS8jGiNRYCOTiILkpS2twAaJ2cE
  • Thread-topic: ( Slightly off topic ) JMS and other messaging

<Snip>
SOAP isn't a messaging protocol.  
</Snip>

From SOAP Version 1.2 Part 1: Messaging Framework:

SOAP Version 1.2 (SOAP) is a lightweight protocol intended for exchanging structured information in a decentralized, distributed environment. It uses XML technologies to define an extensible messaging framework providing a message construct that can be exchanged over a variety of underlying protocols. The framework has been designed to be independent of any particular programming model and other implementation specific semantics.

Kind Regards,
Joe Chiusano
LMI

-----Original Message-----
From: Bill de hÓra
To: 'CHIUSANO, Joseph'; 'Maciejewski, Thomas'
Cc: xml-dev@l...
Sent: 9/18/2002 11:12 AM
Subject: RE:  ( Slightly off topic ) JMS and other messaging


>> CHIUSANO, Joseph:
I consider SOAP to be an XML messaging protocol, so (at least for me)
"messaging vs. SOAP" does not "make sense".  
>>

SOAP isn't a messaging protocol. It can be used as an enveloping
technology for a messaging protocol if there is a messaging protocol to
begin with. For example ebXML has defined a (reliable) messaging
protocol that utilizes SOAP. To offer an analogy, an envelope isn't a
postal service. Saying "messaging vs SOAP" is close to saying "postal
service vs envelope".

Bill de hÓra 
--
Propylon
www.propylon.com 

 


Site Map | Privacy Policy | Terms of Use | Trademarks
Free Stylus Studio XML Training:
W3C Member