axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Reitzel, Charlie" <CReit...@arrakisplanet.com>
Subject RE: SOAPAction
Date Thu, 08 Feb 2001 18:22:10 GMT
A couple thoughts:

First, a reasonable use of the SOAPAction transport header would be to
contain the service URI in the event that it is either a) different than the
transport service address -like a virtual host- or b) the transport message
body is multi-part MIME.  This use of the header would allow URI dispatch
without unbundling or interpreting the message body in any way.

Second, while SOAP only addresses HTTP headers, there's no good reason to
not a apply consistent approach to SMTP and JMS headers.  The same logic
applies.

Charles Reitzel

-----Original Message-----
From: Aleksander Slominski [mailto:aslom@cs.indiana.edu]
Sent: Thursday, February 08, 2001 1:32 AM
To: axis-dev@xml.apache.org
Subject: Re: SOAPAction


James Snell wrote:

> 2. Dispatching based on HTTP SOAPAction header or similar 
>    transport layer specific mechanism
>
>The utility of the SOAPAction HTTP header as defined by 
>the SOAP specification is fuzzy at best.  There are no 
>conventions as to how exactly to use it, nor are there 
>similar mechanisms defined for other transport mechanisms.

Mime
View raw message