• To: Chiusano Joseph <chiusano_joseph@b...>
• Subject: Re: SOA and the Single URL
• From: Rich Salz <rsalz@d...>
• Date: Thu, 04 Aug 2005 12:45:09 -0400
• Cc: "Bullard, Claude L \(Len\)" <len.bullard@i...>, xml-dev@l...
• In-reply-to: <74B14CBC0FEB9D4EB16969F09FA51F4576D316@M...>
• References: <74B14CBC0FEB9D4EB16969F09FA51F4576D316@M...>
• User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7b) Gecko/20040421

> 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

• Follow-Ups:
  • Re: SOA and the Single URL
    • From: Mark Baker <distobj@a...>
  • Re: SOA and the Single URL
    • From: Robert Koberg <rob@k...>

• References:
  • RE: SOA and the Single URL
    • From: "Chiusano Joseph" <chiusano_joseph@b...>

• Prev by Date: RE: SOA and the Single URL
• Next by Date: RE: SOA and the Single URL
• Previous by thread: RE: SOA and the Single URL
• Next by thread: Re: SOA and the Single URL
• Index(es):
  • Date
  • Thread