On Wednesday 06 March 2013 10:15 PM,
Lewis, Keith wrote:
type="cite">This sound difficult to implement and it is not clear
that it is needed.
Isnt it simply the HTTP session of the HTTP request that did the
upgrade? What is the implementation issue here?
But there can be multiple sip application sessions created because
The http sessions are accessed by via the jsessionid.
A web container expects to get the jsessionid cookie in every
message and so would not normally have it stored.
We already have the method SipApplicationSession.getSession(id,
Protocol.HTTP) which can locate a particular http session. The
sessionId can be passed from the client in a SIP message.
the SIP traffic in the websocket connection. Hope you are not saying
that the httpsession should be associated with all of them.
On Tue, Mar 5, 2013 at 6:48 AM, Binod <
To follow up on our discussion in the last meeting, here is
my proposal on handling converged application scenario.
Note that this is applicable only for converged containers.
Standalone SIP containers are not required to support this
It is often useful for developers who embed sip web socket
endpoints into a larger web application (eg: a webrtc app) to
able to share information on a per client basis between the
resources (JSPs, JSFs, Servlets for example) and the web
endpoints servicing that client. Because web socket
are initiated with an http request, there is an association
the HttpSession under which a client is operating and any web
sockets that are established within that HttpSession.
Add a method in SipSessionsUtil to retrieve the HttpSession.
HttpSession httpSession = ssu.getInitiatingWebSession(sipSession);
Let me know what do you think.
On Wednesday 27 February 2013 08:58 PM, Binod wrote:
Please find a draft version of SIP over websocket
This is as per the discussions we had in the F2F.
However, I am thinking, if we should have a way to
obtain HTTP Session
that originated the websocket traffic to the
application. That can help
developers write interesting converged application that
use HTTP and SIP
Note: The information contained in this message may be privileged and confidential
and protected from disclosure. If the reader of this message is not the intended
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 this
communication in error, please notify us immediately by replying to the message and
deleting it from your computer. Thank you. Thrupoint, Inc.