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

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

From: Martin Gudgin <marting@develop.com>
Date: Mon, 7 May 2001 08:02:53 +0100
Message-ID: <008201c0d6c3$be3ed710$0300a8c0@greyarea>
To: "Jake Savin" <jake@userland.com>, "Painter, Philip" <Philip.Painter@compaq.com>, <frystyk@microsoft.com>, "'Daniel Barclay'" <Daniel.Barclay@digitalfocus.com>
Cc: <xml-dist-app@w3.org>
Hi Jake,

Thanks for the info and the link. I read the soapbuilders post which
answered my other question; 'How does SOAPAction relate to the request
URI?', answer; 'It doesn't'

I'm tempted to build a table of SOAPAction usage vs. implementation.
Categories off the top of my head would be; dispatching ( figuring out which
piece of code to run ), routing ( figuring out where the message should
go ), filtering ( figuring out whether the message should be allowed
through ), fixed ( some fixed value, e.g. ebxml ). Anyone got any others?
Would such a table be useful?

I'd say Frontier was in the dispatching category.


Martin Gudgin
Received on Monday, 7 May 2001 03:04:32 UTC

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