Suresh Venkatraman wrote:
I think Suresh's point was that SOAP is not a transport or messaging protocol, but a message format that can be carried over such protocols. E.g., there are (AFAIK) four transport/messaging bindings for SOAP: HTTP, SMTP, BEEP, and XMPP.Yes, that was my point. It's a bit tricky since in RFC 3288, SOAP is mentioned as a XML-based messaging protocol.
That text is still in RFC 4227 but I think we should depend on the SOAP specs to correctly characterize what SOAP is.
Peter -- Peter Saint-Andre Jabber Software Foundation http://www.jabber.org/people/stpeter.shtml
smime.p7s
Description: S/MIME Cryptographic Signature
_______________________________________________ dix mailing list [email protected] https://www1.ietf.org/mailman/listinfo/dix
