Alternate transports for web-services

SOAP Web Services are almost always talked about in relation to HTTP, as HTTP is the most common transport mechanism. However, the SOAP specification is written such that the messages can be sent over a variety of protocols. Persistent connections such as Jabber or HTTP-R could provide improved performance when multiple calls are required.

Or, if you have other needs, carrier pigeons are also fully supported. Read the RFC.

This entry was posted in Uncategorized by Sam. Bookmark the permalink.

Leave a Reply

Your email address will not be published. Required fields are marked *


You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>