[
Lists Home |
Date Index |
Thread Index
]
but really both are just interfaces to the underlying code that is being
implemented.
to have two processes talk to each other I can use messaging or use soap (
OVER HTTP??? )
I guess the true comparison is the messaging client vs. soap ...
Would the competition be jms vs. soap ?
Or a messaging API vs. soap?
-----Original Message-----
From: Bill de hÓra [mailto:bill.dehora@propylon.com]
Sent: Wednesday, September 18, 2002 11:12 AM
To: 'CHIUSANO, Joseph'; 'Maciejewski, Thomas'
Cc: xml-dev@lists.xml.org
Subject: RE: [xml-dev] ( 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
------------------------------------------------------------------------------
This message is intended only for the personal and confidential use of the designated recipient(s) named above. If you are not the intended recipient of this message you are hereby notified that any review, dissemination, distribution or copying of this message is strictly prohibited. This communication is for information purposes only and should not be regarded as an offer to sell or as a solicitation of an offer to buy any financial product, an official confirmation of any transaction, or as an official statement of Lehman Brothers. Email transmission cannot be guaranteed to be secure or error-free. Therefore, we do not represent that this information is complete or accurate and it should not be relied upon as such. All information is subject to change without notice.
|
