Logout latency

stephenlam

Hello,

I have a problem on user logoff. we found that if we execute engine.changeStatus("DISCONNECTED") on web client,

engine.policy.setIdleTimeout(10);
engine.changeStatus("DISCONNECTED");

Lightstreamer server receive such acknowledge after 30 seconds.

16-Jun-08 16:27:50,432 |DEBUG|.metadata.TeletextMetadataAdapter|FOR PUMPS PARKING DESTROYER|notifySessionClose: session [S483511766N20]logged out

Can we minimize the latency?

Thanks!

Alessandro Alinone

You could want to work on the timeouts configuration to reduce time that passes between a stream connection physical close and the notifySessionClose() callback. Such time is mainly controlled by the session_timeout_millis element in lightstreamer_conf.xml. The reason for the existence of this timeout is to let a session survive content-length exhaustions and accept rebind connections. This timeout should just consider network latency and client slowness. Recently, we reduced its default value to 5 seconds, but you could reduce it even more if you want to get a more precise presence tracking.

stephenlam

Thanks! session_timeout_millis elements can shortens timeout latency.

Instead of timeout, Does Lightstreamer support logout function? Can Ligthtstreamer server receive notifySessionClose()callback immediate when Web client execute engine.changeStatus("DISCONNECTED") ?

Alessandro Alinone

At present, notifySessionClose() is only called after the timeout. In a future version of Lightstreamer we will probably change this behavior.