The problem is i guess, that you access the http session outside of a
normal http request cycle
So tomcat doesn't notice anything
And also is it not a spec or behavior requirement that you don't hold on
to your http session objects outside of requests?
On 1 December 2013 15:33, Nir A
Can you come up with an alternative ? Or can you think of a way to fool
tomcat in thinking its in a regular cycle?
On Dec 2, 2013 3:16 PM, Johan Compagner jcompag...@servoy.com wrote:
The problem is i guess, that you access the http session outside of a
normal http request cycle
So tomcat
On Sun, Dec 1, 2013 at 4:33 PM, Nir A n...@netomedia.com wrote:
My POC web application has one html page with javascript web socket
send\recieve messages.
What i did notice that might shade light on whats the problem is the
following scenario:
If i press f5 on the browser, the web page is
Yeah but, I would like to link the websocket session with the http session
of the handshake. and that way i will be able to imitiate the session
replication abilities for websocket.
This mechanism works as intended only problem is the replication not
replicate http session attribute while the
