Re: Protocol Bindings

So would a fair summary of your position be that we produce a companion spec
like:
    Mapping the BEEP Core onto TCP
    http://www.ietf.org/rfc/rfc3081.txt?number=3081

(but of course this would have another name, like "Mapping SOAP onto HTTP")

Jean-Jacques.

Henrik Frystyk Nielsen wrote:

> [...] However, we all know
> that SOAP and XML are not alone in the world - there are plenty of
> existing protocols and infrastructure around. In order to allow SOAP
> based applications to take advantage of such services and features, we
> allow SOAP to be bound to various other protocols in as straightforward
> a way as possible.
>
> This gives us what we want in that it allows SOAP applications to use a
> variety of underlying protocols without us having to define a new
> complex "binding language" that can support extensibility etc. [...]