XML Protocol: Proposals to address SOAPAction header

> Proposal A:
> Use of SOAPAction is discouraged.  SOAPAction is an optional part of XMLP,
> supported but not required.  Services MAY require SOAPAction and any
> software wishing to access those services MUST be able to send it.
>
> Proposal  B:
> Use of SOAPAction is deprecated.  Senders SHOULD NOT send SOAPAction.
> Receivers MUST NOT accept or reject messages on the basis of the presence,
> absence, or value of the SOAPAction header.


I would prefer option B.

Option A will lead to incompatibilities and
confusion. Plese keep the standard simple and clear.

Best regards,
Stefan Haustein

-- 
Stefan Haustein             
Univ. Dortmund, FB 4, LS 8   tel: +49 231 755 2499
Baroper Str. 301             fax: +49 231 755 5105
D-44221 Dortmund (Germany)   www-ai.cs.uni-dortmund.de

Received on Friday, 8 June 2001 12:52:22 UTC