Most people seem to agree that web service orchestration will primarily occur through an asynchronous, document based architecture. One should also assume that some level of guarantee is required (the package arrived in whole, the package arrived intact, the content of the package makes sense, etc.)
I'm hoping that someone has done a comparsion of potential wire protocols for delivering asynchronous, SOAP messages in an open format. If so, please drop me a note.
Compare / contrast the following wire protocols as potential vehichles for delivering asynch. SOAP messages:
- BEEP
- HTTPR
- AWSP
- SMTP
(or others that I may be missing, for now I'm not interested in vendor specific or platform specific stuff)
SOAP 1.1 binding to BEEP:
http://www.ietf.org/rfc/rfc3288.txt
SOAP 1.2 binding to SMTP:
http://www.w3.org/TR/soap12-email
Note that the SMTP binding has a field for message correlation.
SOAP 1.2 binding to SMTP Illustration:
http://www.w3.org/2000/xp/Group/2/02/emailbinding.html
AWSP to SOAP (not really a binding...) :
http://www.trans-enterprise.com/technology/aws/awsp.html
Other:
Generic SOAP binding framework (proposal):
http://www.w3.org/2000/xp/Group/1/10/12/Binding_Framework_Proposal
SOAP binding to HTTP:
http://www.w3.org/2000/xp/Group/1/10/11/2001-10-11_Framework_HTTP_Binding
No comments:
Post a Comment