[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

Re: What does SOAP really add?

• To: Joshua Allen <joshuaa@m...>, xml-dev@l...
• Subject: Re: What does SOAP really add?
• From: Paul Prescod <paul@p...>
• Date: Tue, 23 Apr 2002 13:43:27 -0700
• Cc: Julian Reschke <julian.reschke@g...>
• References: <4F4182C71C1FDD4BA0937A7EB7B8B4C104F0566C@r...>

Joshua Allen wrote:
> 
> > But data exposed using SOAP usually cannot retrieved using GET, and
> > therefore isn't easily accessible using XSLT's document() function.
> 
> XSLT document() can't do POST either.  Saying that "all things that do
> not use GET are inaccessible to GET", is not informative.  I understood
> Paul's position, but I think it's a circular argument.

It isn't so much an argument as a fact. Google's HTTP-based service was
accessible to document() and XPointer and RDF assertions and the new one
isn't.

I really don't see the relevance of XSLT having access to POST. XSLT has
access to HTTP GET because HTTP was designed to be a web protocol and so
it defines a first class "get me the data" method. FTP wasn't designed
for the Web but also has such a feature. Even SMB (through file: and
smb:), IMAP (through imap:) and LDAP (through ldap:) could be used with
XSLT because they have all been adapted to the needs of the Web:

 http://www.w3.org/Addressing/schemes

At least in theory if not in practice.

SOAP has no equivalent, so the Google guys necessarily lost that feature
when they moved from HTTP to SOAP.

 Paul Prescod

• References:
  • RE: What does SOAP really add?
    • From: "Joshua Allen" <joshuaa@m...>

• Prev by Date: RE: What does SOAP really add?
• Next by Date: RE: What does SOAP really add?
• Previous by thread: Re: What does SOAP really add?
• Next by thread: RE: What does SOAP really add?
• Index(es):
  • Date
  • Thread