[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: Marc de Graauw <marc@m...>
• Subject: Re: What Does SOAP/WS Do that A REST System Can't?
• From: Bill de hÓra <bill.dehora@p...>
• Date: Tue, 05 Apr 2005 14:16:37 +0100
• Cc: "'Bullard, Claude L \(Len\)'" <len.bullard@i...>, xml-dev@l...
• In-reply-to: <200504051139.j35BdXDR050954@s...>
• References: <200504051139.j35BdXDR050954@s...>
• User-agent: Mozilla Thunderbird 1.0.2 (Windows/20050317)

Marc de Graauw wrote:

> IMHO REST just does not map easily to request/response patterns where the
> request itself is complex.

By complex, do you mean lots of criteria or do mean something like or'd 
queries? For the latter, systems generate long URIs all the time, (like 
Bugzilla). I know some people don't like long URIs for aesthetic 
reasons, but that's not a good enough reason to use controller URIs (for 
GET or POST). Mind you I believe HL7 is a monster of a format...

If you decide to go the POST route, what you want to avoid  are exposing 
controller URIs (all client requests go to one URI). At least give the 
things of interest (the equivalent of your objects in your domain model 
or your table rows in your physical data model) visible identity.

cheers
Bill

• Follow-Ups:
  • Exposing resources/services vs hiding implementation details
    • From: Michael Champion <michaelc.champion@g...>
  • 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...>

• Prev by Date: RE: Replacing the XML parser in JRE 1.4&later
• Next by Date: Re: Replacing the XML parser in JRE 1.4&later
• 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