ietf
[Top] [All Lists]

Re: SOAP/XML Protocol and filtering, etc.

2001-05-06 13:00:02

On Sun, May 06, 2001 at 03:12:08PM -0400, Keith Moore wrote:
and client APIs.  It also keeps HTTP servers from having to know
specifically whether a particular URI corresponds with a SOAP 
request (in which case it might have to look at the SOAPAction header 
in order to know how to handle it) or not (in which case the SOAPAction
header should be ignored).

Yep; seems to me that Content-Type ss more appropriate for dispatch,
if doing it in a header is desireable.


The name of the SOAP service should *not* be inferred from the XML 
namespace used to describe the request.  This would make it impossible 
to have multiple services that accept identically formatted requests.

The idea is that the identity (i.e., "this is a stockquote service")
is implied by the namespace, and therefore is useful for firewall
admins, etc., so they can work at the granularity of a service type.
The location of the service is still carried in the HTTP
request-line. SOAPAction isn't intended to uniquely name services.



-- 
Mark Nottingham, Research Scientist
Akamai Technologies (San Mateo, CA USA)