Lists Home |
Date Index |
On Thu, Aug 04, 2005 at 12:45:09PM -0400, Rich Salz wrote:
> There is another way to look at it. The message is routed based on its
> contents; the URL is just the "main entrance," through which all
> messages have to come in. The contents of the message itself let the
> receiver determine where, internally, the message should be processed.
> I wouldn't exactly call that a service since it's usually invisible to
> sender and ultimate receiver.
Careful! The "Ultimate receiver" (in SOAP speak) in that case *is*
the recipient of the message, identified by the URI, since it terminates
the message. If it chooses to pass the data it receives along to some
other service, it needs a whole new SOAP message to do so.
IMO, it's most definitely a service. In fact, all RESTful services
which accept documents work this way; document-in, (optional)
Mark Baker. Ottawa, Ontario, CANADA. http://www.markbaker.ca
Coactus; Web-inspired integration strategies http://www.coactus.com