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 really add?
by Julian Reschke other posts by this author
Apr 23 2002 2:17PM messages near this date
Re: [xml-dev] What does SOAP really add? | Re: [xml-dev] What does SOAP really add?
>  From: Didier PH Martin [mailto:martind@[...].com]
>  Sent: Tuesday, April 23, 2002 4:08 PM
>  To: Alaric Snell; Joshua Allen; Julian Reschke; xml-dev@[...].org
>  Subject: Re: [xml-dev] What does SOAP really add?
> 
> 
>  Hi Alaric,
> 
>  Alaric said:
>  > I always felt that XSLT was intended to be purely functional, a language
>  > without side effects - I don't remember seeing a defined operational
>  > semantics (saying what order actions are taken in), just denotational
>  (saying
>  > where information is taken from and what is done to it) :-)
>  > Putting POST capability into XSLT would break this, since (depending on
>  the
>  > XSLT engine in use) a document-post(url) might cause zero, one, or any
>  number
>  > of actual POSTs unless that function alone had a partial operational
>  > semantics defined... which would be a bit hairy
> 
>  Didier replies:
>  Can you explain to me how an HTTP POST brings more side effects
>  than an HTTP
>  GET. Off course, when used in the context of the "document" function (or

Sure.

HTTP GET is supposed to be a side-effect free operation. HTTP POST isn't.

>  anything else having the same intent: fetching an XML document). The basic
>  goal of any construct like the "document" function is to fetch an XML
>  document. Any other construct that would replace/expand it, would have the
>  same intent. So, I am anxious to read your arguments of how an HTTP POST
>  will bring more side effects than an HTTP GET (in the context of
>  fetching an
>  XML document and incorporating it into an infoset). This will expand my
>  knowledge :-)

I think the TAG would argue that if you have a POST operation which is
side-effect free, you should have made it a GET in the first place.


-----------------------------------------------------------------
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://lists.xml.org/ob/adm.pl> 
Thread:
Joshua Allen
Didier PH Martin
Paul Prescod
Didier PH Martin
Didier PH Martin
Jeff Greif
Paul Prescod
Paul Prescod
Didier PH Martin
Paul Prescod
Paul Prescod
Thomas B. Passin
Didier PH Martin
Didier PH Martin
Thomas B. Passin
Paul Prescod
Paul Prescod
Paul Prescod
Didier PH Martin
Didier PH Martin
Alaric Snell
Didier PH Martin
Didier PH Martin
Julian Reschke
John Cowan
Alaric Snell
Jim Ancona
Didier PH Martin
Alaric Snell
Jim Ancona
John Cowan
Thomas B. Passin
Didier PH Martin
Michael Kay
Francis Norton
Adam Turoff
Mike Brown
Julian Reschke
Alaric Snell
Nischal Muthana
Thomas B. Passin
Didier PH Martin
John Cowan
Didier PH Martin
John Cowan
Trevor Croll
Peter Murphy
Didier PH Martin
Didier PH Martin
Paul Prescod

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