[bt-spec] BTP Issue 7 : SOAP RPC

[BTP issues maintainer <peter.furniss@choreology.com>]

This issue has been added to the BTP issue list

BTP Issue 7 : SOAP RPC

Source: Alastair Green, Choreology
Category: technical
Description:
Existing SOAP binding does not allow for use of SOAP RPC model, which is
inefficient, and makes it hard to construct thin clients without
listening capacity, using standard SOAP programming toolkits.
Proposed resolution:
in summary from informal messaging meeting in London, 1 November; more detail to follow.

Create outer wrappers <btp:transmission> and <btp:transmissionResponse> to surround existing <btp:messages>. Receiver can choose to send reply messages back in either wrapper, and can choose to use response message of RR carrier such as HTTP, or to send the reply as an independent one-way or RPC. Empty SOAP envelope or carrier ack to be ignored. Original sender must be prepared to receive messages either on carrier response or via listener. If reply-address is empty then reply must go in carrier response. Illegal value if carrier is non-RR.

---

To comment on this issue, please follow-up to this announcement on the bt-spec@lists.oasis-open.org (replying to this message should automatically send your message to that list).

The issues list will shortly be moved to the oasis website. The current draft, with line numbers is available in pdf format and word format.

To add a new issue, please email to Peter Furniss peter.furniss@choreology.com. It helps if you propose a category (technical, minor technical, editorial, minor editorial).