• To: "Bullard, Claude L (Len)" <len.bullard@i...>
• Subject: Re: Exposing resources/services vs hiding implementation details
• From: Rich Salz <rsalz@d...>
• Date: Tue, 05 Apr 2005 16:25:13 -0400
• Cc: xml-dev <xml-dev@l...>
• In-reply-to: <15725CF6AFE2F34DB8A5B4770B7334EE07206D90@h...>
• References: <15725CF6AFE2F34DB8A5B4770B7334EE07206D90@h...>
• User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7b) Gecko/20040421

> Is this approach (a single URI) a means to unify multiple 
> services under one dispatching service (eg, receives the 
> message, reads it, determines who should do the work, 
> sends that on with details)?

Yes.

Having everyone from the outside come in through a single door has its 
benefits.  Maybe not for everyone, and not all the time, but you can't 
just dismiss it.

	/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: Exposing resources/services vs hiding implementation details
    • From: Robert Koberg <rob@k...>
  • Re: Exposing resources/services vs hiding implementatio n details
    • From: Mark Baker <distobj@a...>

• References:
  • RE: Exposing resources/services vs hiding implementation details
    • From: "Bullard, Claude L (Len)" <len.bullard@i...>

• Prev by Date: RE: Exposing resources/services vs hiding implementation details
• Next by Date: Re: Exposing resources/services vs hiding implementationdetails
• Previous by thread: RE: Exposing resources/services vs hiding implementation details
• Next by thread: Re: Exposing resources/services vs hiding implementatio n details
• Index(es):
  • Date
  • Thread