• To: "algermissen@a..." <algermissen@a...>
• Subject: Re: Exposing resources/services vs hiding implementationdetails
• From: Rich Salz <rsalz@d...>
• Date: Tue, 5 Apr 2005 19:44:05 -0400 (EDT)
• Cc: xml-dev <xml-dev@l...>
• In-reply-to: <4252F528.5050503@t...>

On Tue, 5 Apr 2005, Jan Algermissen wrote:

> With REST you'd have:

The sub-thread start with the assumption that it was "okay" to POST
a complicated query.  Bill then suggested subdividing the URL space
to expose the schema or object model, or something similar.  I was
pointing out some downsides to that.

Somehow this got mutated into a REST discussion (I didn't realize
that was the point behind your post; I thought you bought into
the "POST okay" assumption underlying this thread).

        /r$

-- 
Rich Salz                  Chief Security Architect
DataPower Technology       http://www.datapower.com
XS40 XML Security Gateway  http://www.datapower.com/products/xs40.html

• References:
  • Re: Exposing resources/services vs hiding implementationdetails
    • From: Jan Algermissen <jalgermissen@t...>

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