ASPN ActiveState Programmer Network
ActiveState
/ Home / Perl / PHP / Python / Tcl / XSLT /
/ Safari / My ASPN /
Cookbooks | Documentation | Mailing Lists | Modules | News Feeds | Products | User Groups


Recent Messages
List Archives
About the List
List Leaders
Subscription Options

View Subscriptions
Help

View by Topic
ActiveState
.NET Framework
Open Source
Perl
PHP
Python
Tcl
Web Services
XML & XSLT

View by Category
Database
General
SOAP
System Administration
Tools
User Interfaces
Web Programming
XML Programming


MyASPN >> Mail Archive >> xml-dev
xml-dev
Re: [xml-dev] What Does SOAP/WS Do that A REST System Can't?
by Joe Gregorio other posts by this author
Apr 5 2005 6:45AM messages near this date
RE: [xml-dev] What Does SOAP/WS Do that A REST System Can't? | Re: [xml-dev] What Does SOAP/WS Do that A REST System Can't?
& XSLT On Apr 5, 2005 7:39 AM, Marc de Graauw <marc@[...].com>  wrote:
>  I've got an actual project I wasn't able to do with REST in a satisfactory
>  way (although I would have liked to).
>  
>  I have been writing a SOAP/WSDL specification for HL7v3 messages for the
>  Dutch Health Authority.
>  
>  Those HL7v3 messages are in XML, and derived from older (v2) non-XML
>  formats, so the messages themselves have a quite venerable age. As an
>  example, an important class of messages is query/response. An example I've
>  been working on is a query with (among others) a patient id, which gets a
>  response with all medication that has been prescribed to this patient. In
>  HL7v3 the queries themselves have a lot of elements. With SOAP this is not
>  much of a problem: both the query and response are XML messages. With REST I
>  have the following options:
>  - Use GET, and translate the query to a URI. Now I have two different
>  formats for query and response, and an awful long and hard-to-read URI.
>  - Use POST to send the XML query and fetch the XML response. This is not
>  very RESTful, since the patient's medication history in the response is
>  naturally a resource, and GET is the RESTful way to retrieve a resource. (If
>  I follow this solution, I would end up using POST for all or almost all
>  HL7v3 interactions. If I add an envelope and headers, I've almost got SOAP
>  over HTTP.)

POST is perfectly appropriate for such large queries. If you wanted to 
do that query multiple times then you can create a new URI 
while handling the POST and return that URI with the results. That newly
created URI would allow you to do a GET to perform the same query 
as the inital POST. 

   -joe

-- 
Joe Gregorio        http://bitworking.org

-----------------------------------------------------------------
The xml-dev list is sponsored by XML.org <http://www.xml.org> , an
initiative of OASIS <http://www.oasis-open.org> 

The list archives are at http://lists.xml.org/archives/xml-dev/

To subscribe or unsubscribe from this list use the subscription
manager: <http://www.oasis-open.org/mlmanage/index.php> 
Thread:
Claude L Bullard
Marc de Graauw
Joe Gregorio
Bill de hÓra
Michael Champion
Uche Ogbuji
Jan Algermissen
Uche Ogbuji
Rich Salz
Jan Algermissen
Rich Salz
Michael Champion
Bill de hÓra
Michael Champion
Uche Ogbuji
Bill de hÓra
Robert Koberg
Peter Hunsberger
Michael Champion
Leigh Dodds
Jan Algermissen
Leigh Dodds
Bill de hÓra
Michael Champion
Leigh Dodds
Michael Champion
Rick Marshall
Bill de hÓra
Robert Koberg
Rich Salz
Leigh Dodds
Rich Salz
Leigh Dodds
Rich Salz
Leigh Dodds
Andrzej Jan Taramina
Rich Salz
Bob Foster
Jan Algermissen
Mark Baker
Michael Champion
Michael Champion
Mark Baker
Mark Baker
Michael Champion
Bill de hÓra
Rich Salz
David Lyon
Rich Salz
Joe Gregorio
Rich Salz
Joe Gregorio
Saptagirisa N
Arvind Singh
Rich Salz
Joe Gregorio
Rich Salz
Joe Gregorio
Rich Salz
Dave Pawson
Mark Baker
Joe Gregorio
Mark Baker
Rich Salz
Michael Champion
Elliotte Rusty Harold
Joe Gregorio
Michael Champion
Jan Algermissen
Bill de hÓra
Joe Gregorio
Charles Woerner
Rich Salz

Privacy Policy | Email Opt-out | Feedback | Syndication
© ActiveState Software Inc. All rights reserved