• To: Rich Salz <rsalz@d...>
• Subject: Re: Exposing resources/services vs hiding implementation details
• From: Robert Koberg <rob@k...>
• Date: Tue, 05 Apr 2005 15:35:23 -0700
• Cc: xml-dev <xml-dev@l...>
• In-reply-to: <4252F429.2060703@d...>
• References: <15725CF6AFE2F34DB8A5B4770B7334EE07206D90@h...> <4252F429.2060703@d...>
• User-agent: Mozilla Thunderbird 1.0 (Macintosh/20041206)

Rich Salz wrote:
>> 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.

But once they are in the door, there are other doors they may or may not 
be allowed access. Why let them in the all-knowing door (parse the 
message) when you can lock some of the doors. If they try to enter a 
door they do not have rights to, then send them to room 101 for 
educational (there you put their head in a box of rats).

-Rob

> 
>     /r$
> 

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

• Prev by Date: Re: What Does SOAP/WS Do that A REST System Can't?
• Next by Date: Re: Exposing resources/services vs hiding implementationdetails
• Previous by thread: Re: Exposing resources/services vs hiding implementatio n details
• Next by thread: RE: Exposing resources/services vs hiding implementation details
• Index(es):
  • Date
  • Thread