xml-dev - Re: [xml-dev] Exposing resources/services vs hiding implementation detai

Re: [xml-dev] Exposing resources/services vs hiding implementation detai

[ Lists Home | Date Index | Thread Index ]

To: "Bullard, Claude L (Len)" <len.bullard@intergraph.com>
Subject: Re: [xml-dev] Exposing resources/services vs hiding implementation details
From: Rich Salz <rsalz@datapower.com>
Date: Tue, 05 Apr 2005 16:25:13 -0400
Cc: xml-dev <xml-dev@lists.xml.org>
In-reply-to: <15725CF6AFE2F34DB8A5B4770B7334EE07206D90@hq1.pcmail.ingr.com>
References: <15725CF6AFE2F34DB8A5B4770B7334EE07206D90@hq1.pcmail.ingr.com>
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: [xml-dev] Exposing resources/services vs hiding implementation details
  - From: Robert Koberg <rob@koberg.com>
- Re: [xml-dev] Exposing resources/services vs hiding implementatio n details
  - From: Mark Baker <distobj@acm.org>

References:
- RE: [xml-dev] Exposing resources/services vs hiding implementation details
  - From: "Bullard, Claude L (Len)" <len.bullard@intergraph.com>

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