Script session identity

I am developing a monitoring application which is intended to live very long.
Thus, I have replaced the DefaultScriptSessionManager with my own
implementation providing a "session garbage collector", which checks at a
given interval if the client of a scripting session still lives (by calling
a script method via reverse AJAX). This is necessary to free large memory
allocations done by a session during lifetime.

Now comes the tricky point: As the client may not respond, the session is
removed at the server. But, if the client has just been disconnected (e.g.
by network failure) it starts to call the server again. The session manager
does not find the session in its list and creates a new one. This will lead
to errors at the client side because the server state does not match the
client.

Is there a possibility to determine if a session is active on the client
side without storing the ids of the terminated sessions at the server?
Further, it should not be necessary to intercept any @RemoteMethod call for
this check.

Joe had some thoughts in a post to make engine.js "static", generating the
session ids at the server. This would be the proper way for a fresh client
will request a session that has no id assigned yet while active clients
always provide an id. If terminated, there would be the point to inform the
client about the removal.
Will this feature be in the final 2.0 release?

Thanks,
Thomas


-- 
View this message in context: 
http://www.nabble.com/Script-session-identity-tf3251846.html#a9039575
Sent from the DWR - Users mailing list archive at Nabble.com.