Re: CGI::Session or CGI::Application

[prev] [thread] [next] [Date index for 2005/01/16]

sofadmin@xxxxxxx.xxx wrote:
> Interesting, your comments on CGI::Session vs Apache::Session as I've had
> nothing but trouble with Apache::Session::File -- session data
> inconsistently being written to the file. 

I'm sorry to hear that. Did you mention those problems to the author or 
bring it up on the mod_perl list? Were you using just 
Apache::Session::File or Apache::Session::Flex? I suspect that it was 
having issues with locking the files so maybe trying another locking 
mechanism (using Flex) might have helped. But that's just a guess.

> Several years ago I first tried
> Apache::Session, but had the problem with data being saved in the session,
> so tried CGI::Session, which at the time also used a tied hash &
> everything worked fine (used ::File & ::MySQL, both). Unfortunately, a
> recent server upgrade forced a CGI::Session module upgrade -- & the newer
> module had removed the tied hash implementation in favor of an object
> oriented one. Couldn't find the older module with tied hash implementation
> anywhere, so quickly changed to using Apache::Session for those sites that
> were using the session module. The ::MySQL module seems OK, but the ::File
> module had same problem as before - inconsistent writing of data to the
> session. So, I had to scramble to re-write code for several sites to
> implement the 'new' CGI::Session oo implementation. Do you use the
> Apache::Session::File module or one of the others?

Sorry, I only use Apache::Session::MySQL (or Apache::Session::Flex with 
a store of MySQL). I use MySQL over File because it's *so* fast for 
primary key lookups. If you have any kind of traffic, I can guarantee 
that it'll be faster than using a straight file, and since it's not any 
harder to setup (except creating the table, but then they give you the 
sql for that) I always go with the faster option :)

        -- 
        Michael Peters
Developer
Plus Three, LP