As far as I know, memcached runs in-memory and does not have a persistent backing-store.
Currently my team is not ready yet to use memcached.
So, I plan to write a simple database backed alternative.
My question is pretty much in similar vein to this other question
http://stackoverflow.com/questions/33619/concurrent-logins-in-a-web-farm
My webapp has clear entry (login) and exit (logout) points.
The plan:
- On login, I will add the userid into a table.
- On logout, I will delete the row containing the userid.
Issues:
Is there a well-used method to timeout a row in Mysql ? By method, I mean a best practice. Once a timeout has been reached, the row is removed.
Thanks
J