On Thu, 2005-02-10 at 17:48 -0200, Leo wrote: > Because application data should be the same across all processes (and I > didn't think to use your suggestioned solutions below) when a request > comes in, I tie the application session, check to see if my modification > counter are equal. If it is then just untie the hash, If the > modification number number has changed then before the untie I do my > data sync operation. It's really an ugly way to keep things from > breaking in my test environment. I got the idea from one of the man > pages that came with Apache::Session I think.
Oh, I see. Another way to do this sort of thing, if you're loading the data from a file, is to stat() the file to see if it has changed since the last time you loaded it. That's more efficient than using Apache::Session. - Perrin
