[bt-spec] Messaging issues

[Alex Ceponkus <alex@ceponkus.org>]

BTPers,

I have been looking over the messaging portion of the spec and have a
concern that might need discussion.

In the case of the SOAP over HTTP binding, the SOAP messages are modeled as
one-way messages, but the underlying transport (HTTP) is request-response.
As it stands right now, a message gets sent (say a BEGIN) and then nothing
at the SOAP layer gets returned, just an HTTP 200 signifying that the SOAP
message was received.  We are currently using an asynch messaging model, so
the response message (the BEGUN) will be sent with a new connection at a
later time.  Here's my concern: I haven't seen too many existing SOAP
implementations that behave this way (soap message over http request, http
only response.)  Typically, a SOAP message with an empty Body is returned.
Are there any objections to returning an empty soap message for the soap
over http binding?

Alex