[bt-spec] BTP Issue 84 : What determines one-shot is used

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

This issue has been added to the BTP issue list

BTP Issue 84 : What determines one-shot is used

Submitter: Choreology
Category: minor technical
Description:
0.9 says that one-shot (ENROL and PREPARED
with CONTEXT_REPLY on application response) is a specialisation (senders option) 
of one-wire, because it is specified that the inferior-side decides if it can 
do one-shot by matching the binding addresses to the address for the application response.

There are various problems with this - among them, it assumes the service-side has an address for the application response to match against, rather than just a pending http response. Since application request/response is the most likely use of one-shot, this is rather important.

An alternative approach is to assume that the service side knows (by application/configuration) that it should do one-shot replies, regardless of the superior address. ENROL and PREPARED are sent with the CONTEXT_REPLY.

A possible complication is that the Superior's address is different from the reply address for the application (or rather the destination of the CONTEXT_REPLY). However, in this case the receiver of the CONTEXT_REPLY (the client-side interceptor/communicator, probably) will know the superior's address (it can/must be assumed to - since it put the CONTEXT there, that is reasonable) and can forward the ENROL and PREPARED to there. This implies ENROL and PREPARED must be related only to the CONTEXT_REPLY for their transaction.

---

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 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).