[bt-spec] BTP Issue 29 : Redirection

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

This issue has been added to the BTP issue list

BTP Issue 29 : Redirection

Submitter: Bill Cox, (for all BEA members)
Submitter's identification: issue H
Submitter's title: Participant timeout impact needs further discussion.
Note: The original title doesn't seem to correspond to the substance
Category: technical
Detail:
(Submitter documents are email from Alistair Green 20011023, BEA 20011018)
Alistair Green's rebuttal, supporting including transport functionality into
BTP, has a sound motivation, but complicates BTP while violating generally
accepted layering approaches. At the least, this belongs in a separate
specification (SOAP with redirection? Generic redirection protocol?). His
argument that it is necessary doesn't mean it should be standardized via a
back door such as BTP.  There are many other things about which one could
make the same argument.  (e.g., reliable messaging, dealing with failed
message routers)
Proposed Remedy:
Eliminate the redirector and related message from the specification.  Submit
this functionality to an appropriate standards group, e.g. W3C XML
Protocols.  In the alternative, break it out clearly as an enhancement to
messaging services, and giving it a separate section to make separate use
easier.

---

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