What I am wondering about is why there doesn't seem to be available code for dealing with existing sessions.. for managing multiple existing open CGI::Sessions. That is at least in regards to when it's saved as a cgi session file.
I have seen this asked before, but I haven't seen it answered.
| [reply] |
Part of the problem leoncharre is that everybody uses CGI::Session differently. As perrin said, you can just use Storable and look at the file, but then you need to know what you are looking for! And you need to know what you put in there. Storable is fast and full of goodness, but it doesn't work for every situation.
We have one instance where we use a single session database shared between three Web-apps. So for that we need to use the database - typically MySQL. The real fun part is that we can, of course, have the different apps on different machines that way. But I think the reason you haven't seen any modular code is because in reality very few people need to peer into the session data for any reason. If you do it is likely that your requirements will be more than minimal and you would need to craft it yourself anyway.
jdtoronto
| [reply] |
For "dealing with existing sessions"? What does that mean? Are you asking why no one has written a utility to run Storable on the files? Probably either no one needed it, or it was so easy that they figured no one else would want the code. Have you tried it? If you're stuck, I'm sure we could help.
| [reply] |