Just remember, you can very easily repopulate the data in session on every
login. If there is no login authentication done, you can use filters to
confirm if the required data exists and if not repopulate them as required.
You don't need to know if session expires just if the data still exists and
I'm already doing a good bit of database batch processing from cronjobs and
wanted to avoid more, so after more thinking about it, I've decided to come
at the problem from a different approach. Instead of trying to write all of
the objects to the database, I'll keep the values for the objects in
There is no such thing, a session may expire also because of user
inactivity thus there is no way to catch this on the server side. Even
in case the browser is closed nothing is sent to the server to signal
the session end (like a logout).
In case you store the user sessions in the database you co
