[Confirmation] Visit automatically nulled on timeout

["F. Da Costa" <da...@xs4all.nl>]

Hi all,

Just wanted to confrm whther my assumption re. the lifecycle is correct.

Setting:
Since i only want a user to be logged in once i keep track of the users in 
a Map contained in the Global object. The map contains the user and its its 
visit as a value.

Logging out normally is easy, just remove from the map.
The interesting part is what to do when the user just 'disappears'.
I am assuming that the visit object times out and will be set to null/ 
removed by the engine. Is this correct?
This would allow me to work on the premise that the user (after abnormal 
connection close) cannot come back until its old visit has timed out.

If anybody has got a more elegant solution or idea, please feel free. I'm 
greenfielding so there are no extremes ;-)

TIA
Fermin DCG


---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org