W3C home > Mailing lists > Public > xml-dist-app@w3.org > August 2001

Re: SOAP and the Web architecture

From: David Crowley <dcrowley@scitegic.com>
Date: Tue, 28 Aug 2001 00:36:54 -0700
Message-Id: <5.1.0.14.0.20010828003021.0430fea0@pop.business.earthlink.net>
To: francis@redrice.com, Paul Prescod <paulp@ActiveState.com>
Cc: xml-dist-app@w3.org

Having a nice GET syntax for a particular service might be nice, but I 
don't see how SOAP could do that.  Even a "simple" SOAP request is a fairly 
long stream of bytes and typing in a hex/base64/whatever encoded stream of 
XML bytes on a command line doesn't sound fun.  Perhaps some of the work 
done in Kafka could help? Some kind of XSLT that could transform a "simple" 
input into a true SOAP message which is then sent (by lynx or whatever) and 
then your XSLT to parse the response...


At 09:48 PM 8/27/2001, Francis Norton wrote:


>Paul Prescod wrote:
> >
> >
> > I have a variety of XSLT stylesheets that I use to extract information
> > from Google and many command line scripts for extracting things from
> > other websites (basically lynx -dump | grep). All of this is going to
> > get more complicated in a post-GET world.
> >
>Yes, one concrete requirement in my book would be a syntax for calling
>SOAP services from XSLT. The document() function is entirely URL based.
>But I don't expect this requirement to be met anytime soon, because SOAP
>is seen as a protocol for doing updates and many XSLT authors are keen
>to prevent it being expanded into a general purpose language.
>
>Francis.
Received on Tuesday, 28 August 2001 03:37:01 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 December 2009 10:59:03 GMT