What implications does this have on the size of the cache that can be
created with IPC::MM
I believe that documentation is telling you that each OS governs the
amount of shared memory you can have in different ways. Linux, for
example, has a variable called shmmax, accessible
as
It's #5 that's troublesome. I wasn't sure how I could expire the older
session (since the session key that matters is sitting client side). I
guess I could keep a table of invalidated session keys, and check
against that every time in along with all the other checks going on in
How are you handling your sessions? I use Apache::Session::Postgres.
In my scenario, if I needed to do this, I would check the list of valid
sessions I have for one that exists for the user. ie, if 'gphat' tries to
login, I check to see if any of the sessions the db are for user gphat
