Skip to main content

[jsr356-experts] Re: Summary: Web Socket Sessions in Distributed Servers

  • From: Mark Thomas < >
  • To:
  • Subject: [jsr356-experts] Re: Summary: Web Socket Sessions in Distributed Servers
  • Date: Fri, 07 Dec 2012 17:50:42 +0000

On 07/12/2012 02:12, Danny Coward wrote:
> So I think that means websocket applications that are 'distributable'
> should not
> - use static variables or local filesystems to store application state
> (use a database instead)
> - put non Serializable data in websocket Sessions
> 
> Let me know if you have more things you think the specification should
> define for deployments on distributed servers.

That implies some API changes. Session and MessageHandler will need to
implement Serializable. I'm guessing that RemoteEndpoint and
ClientContainer can be reconstructed post fail-over.

Do we want to add anything along the lines of
HttpSessionActivationListener? My guess is that if it is required for
HttpSEssion then we'll probably need it for the user properties map.

Mark



[jsr356-experts] Summary: Web Socket Sessions in Distributed Servers

Danny Coward 12/07/2012

[jsr356-experts] Re: Summary: Web Socket Sessions in Distributed Servers

Mark Thomas 12/07/2012

[jsr356-experts] Re: [jsr356-users] Re: Summary: Web Socket Sessions in Distributed Servers

Danny Coward 12/07/2012
 
 
Close
loading
Please Confirm
Close