> Ah - now I see where you're going. Yes, a "dispatcher" service can
> categorized in three ways:
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. For what it's worth, *we* call it an XS-40 :)
/r$
--
Rich Salz, Chief Security Architect
DataPower Technology http://www.datapower.com
XS40 XML Security Gateway http://www.datapower.com/products/xs40.html
