[Home] [By Thread] [By Date] [Recent Entries]

  • To: "Robert Koberg" <rob@k...>, "Rich Salz" <rsalz@d...>
  • Subject: RE: SOA and the Single URL
  • From: "Chiusano Joseph" <chiusano_joseph@b...>
  • Date: Thu, 4 Aug 2005 13:03:06 -0400
  • Cc: "Bullard, Claude L \(Len\)" <len.bullard@i...>, <xml-dev@l...>
  • Thread-index: AcWZFVV7HDMkcV0KSIGetLnn5hjWeAAAPA5g
  • Thread-topic: SOA and the Single URL

> -----Original Message-----
> From: Robert Koberg [mailto:rob@k...] 
> Sent: Thursday, August 04, 2005 12:55 PM
> To: Rich Salz
> Cc: Chiusano Joseph; Bullard, Claude L (Len); xml-dev@l...
> Subject: Re:  SOA and the Single URL
> 
> Rich Salz wrote:
> >> 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.
> 
> This is where I might be missing something (if I may jump in...).
> 
> So each message, no matter the size, should be parsed to 
> determine authorization, authentication and validity? As 
> opposed to stopping/redirecting a request based on the 
> URL/request-credentials before a parse happens?

Yes - it depends on your requirements. Large message sizes are often an
issue with XML (as we well know), so that may certainly be a constraint
on requirements.

Joe

Joseph Chiusano
Booz Allen Hamilton
O: 703-902-6923
C: 202-251-0731
Visit us online@ http://www.boozallen.com
  
> thanks,
> -Rob
> 

Site Map | Privacy Policy | Terms of Use | Trademarks
Free Stylus Studio XML Training:
W3C Member