Web services allow for the delivery of SOAP messages over any protocol. A
common misconception is that all SOAP messages must be transmitted over HTTP.
While that approach is useful in many cases, there are situations where it
makes sense to use alternatives. This paper investigates situations where
HTTP does not scale sufficiently for enterprise Web service deployments and
looks at available alternatives.
HTTP and Scalability
HTTP was designed for serving Web pages under the assumption that the
protocol would only be required to send a request and receive a response.
This paradigm has worked very well for the World Wide Web and has been
ubiquitously accepted as its standard protocol. When a person makes a request
on an interactive Web site, they are typically interactin... (more)