On 6/16/06, RA Jones <[EMAIL PROTECTED]> wrote:
Presumably this is not the correct way to handle new session id generation in CGI::Session. Is it even possible to force CGI::Session to use a pre-defined session id string in the first place?
If CGI::Session can not load a session from the ID given, it throws it away and creates a new one (at least that is the way it looks from the source code). I am not sure why that is done, but that is the way it currently works. One way around this may be to write your own custom ID generator for CGI::Session, and have it look for an existing session ID somewhere and use that, or failing that generate the ID in the usual way. For help on that you are probably better off using the CGI::Session mailing list. This is not something that CAP::Session can do anything about. Cheers, Cees --------------------------------------------------------------------- Web Archive: http://www.mail-archive.com/[email protected]/ http://marc.theaimsgroup.com/?l=cgiapp&r=1&w=2 To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
