Re: SOAP/XML Protocol and filtering, etc.

Does the HTTP spec allow applications to add headers?

If so, what the heck is the argument about?

BTW, I thought SOAPAction was dorky when I first heard the idea. But it's
there.

There's deployment based on SOAPAction.

Dave


----- Original Message -----
From: "Keith Moore" <moore(_at_)cs(_dot_)utk(_dot_)edu>
To: "Dick Brooks" <dick(_at_)8760(_dot_)com>
Cc: <moore(_at_)cs(_dot_)utk(_dot_)edu>; "Henrik Frystyk Nielsen" 
<henrikn(_at_)microsoft(_dot_)com>;
"Mark Nottingham" <mnot(_at_)akamai(_dot_)com>; <ietf(_at_)ietf(_dot_)org>; 
<xml-dist-app(_at_)w3(_dot_)org>
Sent: Tuesday, May 08, 2001 6:25 AM
Subject: Re: SOAP/XML Protocol and filtering, etc.


> > > far better for the SOAP-specific message broker to have intimate
knowledge
> > > of the SOAP-specific payload, than to have the SOAP-specific message
broker
> > > to have intimate knowledge of the HTTP-specific request header.
> > I never said a message broker was SOAP specific.
> a message broker that looks at a SOAPAction header isn't SOAP specific?
>
> > There are message brokers running on HTTP servers that can dispatch
> > processing for EDIINT AS2, GISB EDM, AIAG E-5, ebXML, SOAP and other
types.
> what you are saying is that there are people out there who do not
understand
> the value of clean separation of function between layers.  how is that a
> justification for a standards-setting organization to propagate that
> misunderstanding?
>
> Keith