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

Re: [i95, i22] - Proposal for clarifying use of SOAPAction

From: Jake Savin <jake@userland.com>
Date: Sun, 06 May 2001 18:06:23 -0700
To: Martin Gudgin <marting@develop.com>, "Painter, Philip" <Philip.Painter@compaq.com>, <frystyk@microsoft.com>, "'Daniel Barclay'" <Daniel.Barclay@digitalfocus.com>
CC: <xml-dist-app@w3.org>
Message-ID: <B71B431E.F8A9%jake@userland.com>
Hi Martin,

I recently wrote a note to the SOAPBuilders mailing list which summarized
our use of SOAPAction:


Here's a condensed version of that summary:

First, the presence of a SOAPAction header tells Frontier that an incoming
request is SOAP.

We use the path portion of the value of SOAPAction to find the table in our
object database, which contains the RPC handler -- the script which
implements the RPC method.

For example, SOAPAction: "http://myserver.com/myservice/" means "you'll find
the method I want to invoke in the table named myservice". A SOAPAction
value of "/myservice/" is equivalent.

Which script to execute within that table is determined by the name of the
method element -- the first sub-element of the SOAP Envelope's Body
sub-element. If the method element is <mymethod>, then according to the
SOAPAction above, this would mean "find the script named mymethod in the
table named myservice, call it, and return the results".

SOAPAction is not required to be unique per method.


PS to Martin: Sorry for the re-send. I wanted to make sure others saw this,
and that it posted to the list.

on 5/6/01 2:56 PM, Martin Gudgin at marting@develop.com wrote:

> Philip,
> Could you provide examples of what you put into SOAPACtion and how you use
> that info?
> Cheers
> Martin Gudgin
> DevelopMentor
> ----- Original Message -----
> From: "Painter, Philip" <Philip.Painter@compaq.com>
> To: <frystyk@microsoft.com>; "'Daniel Barclay'"
> <Daniel.Barclay@digitalfocus.com>
> Cc: <xml-dist-app@w3.org>
> Sent: Friday, May 04, 2001 3:01 PM
> Subject: RE: [i95, i22] - Proposal for clarifying use of SOAPAction
>> We are currently using SOAPAction in what I thought was its definition and
>> will continue to do so since we currently have no interop issues. However,
>> for the future there will be interop issues so this has to be resolved. We
>> certainly don't want to go with tying a service to a url 1-2-1.
>> Philip Painter
>> Technology Consultant
>> Compaq Computer Limited
>> Warrington UK
>> Philip.Painter@compaq.com
>> Desk: +44 (0)1925 841233
>> Mobile: +44 (0)7790666784
Received on Sunday, 6 May 2001 21:06:56 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 22:01:13 UTC