Skip to main content

[jsr356-experts] Re: Multithreading Options

  • From: Joe Walnes < >
  • To:
  • Subject: [jsr356-experts] Re: Multithreading Options
  • Date: Wed, 8 Aug 2012 18:56:13 -0500



On Wed, Aug 8, 2012 at 6:47 PM, Greg Wilkins < " target="_blank"> > wrote:
On 5 August 2012 19:05, Mark Thomas < "> > wrote:
> The question this raises for me is what is the mechanism going to be for
> retaining state? i.e. what is the WebSocket equivalent of HttpSession
> going to be? The follow-on question is how is state information
> transferred between the WebSocketSession (for want of a better name
> right now) and the HttpSession.

In my websocket work to date, having websocket session has not been an
issue as we create an EndPoint per connection as a new object that can
hold state.

That's true, but there's also some state that needs to be shared between connections such as authentication credentials.



[jsr356-experts] Re: Multithreading Options

Mark Thomas 08/05/2012

<Possible follow-up(s)>

[jsr356-experts] Re: Multithreading Options

Mark Thomas 08/05/2012

[jsr356-experts] Re: Multithreading Options

Greg Wilkins 08/08/2012

[jsr356-experts] Re: Multithreading Options

Joe Walnes 08/08/2012

[jsr356-experts] Re: Multithreading Options

Justin Lee 08/09/2012

[jsr356-experts] Re: Multithreading Options

Joe Walnes 08/09/2012

[jsr356-experts] Re: [jsr356-users] Re: Multithreading Options

Danny Coward 08/09/2012

[jsr356-experts] Re: [jsr356-users] Re: Multithreading Options

Greg Wilkins 08/11/2012

[jsr356-experts] Re: [jsr356-users] Re: Multithreading Options

Justin Lee 08/11/2012

[jsr356-experts] Re: [jsr356-users] Re: Multithreading Options

Mark Thomas 08/11/2012
 
 
Close
loading
Please Confirm
Close