Hi Jake, In response to the summary http://groups.yahoo.com/group/soapbuilders/message/2803 I pointed out that this is a problematic use of SOAPAction and that it is a bad idea not to take into account the request URI because it fundamentally breaks HTTP. SOAPAction is *not* a replacement for the request-URI and there is nothing in the description in http://lists.w3.org/Archives/Public/xml-dist-app/2001May/0053.html That hints at this use. SOAPAction is much more aligned with the content type in indicating what is *in* the message rather than where it *goes*. >I recently wrote a note to the SOAPBuilders mailing list which >summarized our use of SOAPAction: > >http://groups.yahoo.com/group/soapbuilders/message/2740Received on Monday, 7 May 2001 10:48:47 GMT
This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 December 2009 10:59:01 GMT