* Daedalus ([EMAIL PROTECTED]) wrote: > Sounds like somthing that probably has a module already > written ;-) So, as I start searching through CPAN, I > thought I'd drop a note to the list and see if someone > could shorten my search and send me in the right > direction.
There are a couple of easy ways to do this. (probably more, but these are the ones I have experience with) CGI.pm Apache::Session CGI.pm You create a session id and then dump state to a file (CGI.pm provides methods to do this). And you name your file with the string or your session id upon exiting. When you come back to the script with a session id, the first thing you do is look to see if you have a file and then read that file in to restore state (CGI.pm provides a method for this too) The setback is that if you use a server farm, you need to have a locally mounted directory that is common amoung the servers. If the network connection breaks, your app dies... :( Apache::Session You create a table to store sessions in (Apache::Session has the create statements within the perldoc). Then you just follow the examples within the perldoc. It's very easy to use. This works great and is scalable because you are writing to a database that may or may not be physically associted with your server or servers. Regards -biz- > > Thanks, > -Bill > > -- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > -- __ () __ __ __ __ | o)--(_ | o) =| =| Jeff Bisbee #!/usr/bin/perl -w |__)__|__)__)__|__| [EMAIL PROTECTED] use strict or die; -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
