Patrick Schaaf wrote:
This way there is no longer any correctness problem, and a GC is only
needed to clean up sessions that are never requested again - and for that I
fully agree that a separate - e.g. cron driven - "GC now" job would be best
(not affecting latency of running frontent requests too much).
I've not had much interest in this discussion as I am more than happy with how things work now. It is not unusual for my 'client' sessions to last for an hour or so without activity and their 'automatically' logging out was the problem originally. So now I'm set never to clear session data and run a clear up on the session directory before the site starts work in the morning. There are reasons a system wide approach may be more practical than changing how a single session handles things?
--
Lester Caine - G8HFL
-----------------------------
Contact - http://lsces.co.uk/wiki/?page=contact
L.S.Caine Electronic Services - http://lsces.co.uk
EnquirySolve - http://enquirysolve.com/
Model Engineers Digital Workshop - http://medw.co.uk
Rainbow Digital Media - http://rainbowdigitalmedia.co.uk