Re: B2B and transaction support methods
- From: "Lewis, Keith" <
- To: jsr359-experts <
- Subject: Re: B2B and transaction support methods
- Date: Wed, 10 Jul 2013 15:12:42 +0100
- List-id: <jsr359-experts.sipservlet-spec.java.net>
Thanks for these comments.
There are some that we did not cover in the meeting.
See embedded comments below.
On Wed, Jun 26, 2013 at 4:51 PM, Nitzan Nissim
> I have a few comments:
> * InviteBranch createInviteBranch();
> - Confusing naming, Can this be something that has "UAS" in it?
I am suggesting the term InviteContext instead of InviteBranch so the
method could be createUasInviteContext()
> - Why does it need to be only for INVITE?
> - Does that work only for a B2B application? What about a proxy application
> that had one of its branches requests forked down stream? Here the proxy
> will pass the different UASs tags on the provisional responses on the
> single incoming branch, and choose a single best final response (unless
> there are multiple successful ones). On a B2B app there is no "best
> response" concept, and the app can send both error and success responses
> back to the client.
> Isn't this sort of difference from a B2B be confusing to the developer?
> - As a general note, why does the B2B need to replicate the behavior of a
> proxy? Isn't a B2B different then a proxy since it has more control on the
> dialogs, and doesn't need to send back to the UAC exactly the same messages
> it got from the UAS? Wouldn't an application composer that chose a B2B
> design rather then a proxy, be able to send all the needed data from the
> different UASs back to the UAC on a single dialog, in its own discretion?
> I feel like the concept of "forking back" on the UAS contradicts the SIP
> RFC, and can be pretty confusing and error prone to implement.
> Could you give an example of a use case in which this ability is absolutely
> * SipServletResponse getAcknowledgedResponse();
> Any reason not to make that work on the UAC side as well?
Yes - we can do that. We would still throw an exception if it is used at a
> * Same for isReliableProvisional. I believe its nice to have this work on
> the UAS as well.
Yes - I will change to allow this on an outgoing response that has been
sent. I think we should throw an exception if it is called on a response
that has not yet been sent.
> From: "Lewis, Keith"
> To: jsr359-experts
> Date: 24/06/2013 06:12 PM
> Subject: B2B and transaction support methods
> Hi all,
> I attach a new version of the Thrupoint proposal.
> It now uses a new interface InviteBranch which represents an invite/session
> This allows us to cater for forked invite requests in a cleaner way.
> Note: The information contained in this message may be privileged and
> and protected from disclosure. If the reader of this message is not the
> recipient, or an employee or agent responsible for delivering this message
> to the
> intended recipient, you are hereby notified that any dissemination,
> distribution or
> copying of this communication is strictly prohibited. If you have received
> communication in error, please notify us immediately by replying to the
> message and
> deleting it from your computer. Thank you. Thrupoint, Inc.
> [attachment "PendingTransactionandB2BSupportmethods-v4.pdf" deleted by
> Nitzan Nissim/Haifa/IBM]
Note: The information contained in this message may be privileged and
and protected from disclosure. If the reader of this message is not the
recipient, or an employee or agent responsible for delivering this message to
intended recipient, you are hereby notified that any dissemination,
copying of this communication is strictly prohibited. If you have received
communication in error, please notify us immediately by replying to the
deleting it from your computer. Thank you. Thrupoint, Inc.