HTTP binding concerns

Hi all,

I'm quite concerned about the HTTP binding based on the binding framework.  FWIW,
the framework itself is quite decent as an abstract description of the relationship
(through interfaces) between SOAP and the underlying protocol.  But the HTTP binding
seems more a formal description than a specification that can be easily implemented.
Obviously there's a continuum between clarity and specificity that must be straddled,
but I strongly believe that the current version of the binding is too far to one
extreme at the expensive of the other.

If the HTTP binding were complex enough that simple prose was insufficient to
communicate the details of implementation, then by all means include some tool such
as a state model, flow chart, etc..  But I don't believe the HTTP binding is nearly
that complex.

I would recommend that it be discarded.  Failing that, it could be made informative
while a prose version would be normative.

MB
-- 
Mark Baker, CSO, Planetfred.
Ottawa, Ontario, CANADA.
mbaker@planetfred.com

Received on Monday, 22 October 2001 22:52:56 UTC