[
Lists Home |
Date Index |
Thread Index
]
Absolutely - AKA content-based routing. Of course, this capability could
be represented as an infrastructure service in a service-oriented system
(SOS - gotta love that acronym) - perhaps even with an XS-40 behind
it.;)
Joe
Joseph Chiusano
Booz Allen Hamilton
O: 703-902-6923
C: 202-251-0731
Visit us online@ http://www.boozallen.com
> -----Original Message-----
> From: Rich Salz [mailto:rsalz@datapower.com]
> Sent: Thursday, August 04, 2005 12:45 PM
> To: Chiusano Joseph
> Cc: Bullard, Claude L (Len); xml-dev@lists.xml.org
> Subject: Re: [xml-dev] SOA and the Single URL
>
> > 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
>
|
