[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

Re: What Does SOAP/WS Do that A REST System Can't?

• To: Rich Salz <rsalz@d...>
• Subject: Re: What Does SOAP/WS Do that A REST System Can't?
• From: Leigh Dodds <leigh@l...>
• Date: Tue, 05 Apr 2005 23:34:27 +0100
• Cc: Bill de hÓra <bill.dehora@p...>,xml-dev@l...
• In-reply-to: <42529D77.50608@d...>
• References: <200504051139.j35BdXDR050954@s...> <42528FB5.7040300@p...> <42529D77.50608@d...>
• User-agent: Mozilla Thunderbird 1.0 (Windows/20041206)

Rich Salz wrote:
> As a long-time fan of federated naming (XFN), I'm sympathetic to this 
> approach.  In some deployments, however, we've seen that it's not 
> appropriate:
>     - If you're already POSTing the query, why require clients to
>       know "n" URL's rather than one?  Why "split up" the mesage?

Why do the clients have to known "n" URLs?

POST to a URL.
Receive 302 See Other with a Location header.
Perform a GET on the URL in the Location header to see the results.

Many (all?) HTTP libraries do this sequence automatically. No training
required.

 >     - Concerns about exposing more than a single "generic" URI
 >       to outside parties; more choke-points to manage, more things
 >       to forward/change when deployments or architectures change
 >       internally

And corollary: more flexibility about changing deployment/architecture 
over a site in pieces rather than having to change a single controller
URI or splice in additional functionality.

L.

• Follow-Ups:
  • Re: What Does SOAP/WS Do that A REST System Can't?
    • From: Rich Salz <rsalz@d...>

• References:
  • RE: What Does SOAP/WS Do that A REST System Can't?
    • From: "Marc de Graauw" <marc@m...>
  • Re: What Does SOAP/WS Do that A REST System Can't?
    • From: Bill de hÓra <bill.dehora@p...>
  • Re: What Does SOAP/WS Do that A REST System Can't?
    • From: Rich Salz <rsalz@d...>

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