On Mon, 2004-03-22 at 13:04, Chris Ochs wrote:
> Rather than passing stuff around in globals or via pnotes, I was thinking
> about making a request object and then using an all OO structure. Modules
> that have functions that are called via callbacks could have a new() method
> that is called befo
: "Chris Ochs" <[EMAIL PROTECTED]>
To: "Perrin Harkins" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Sunday, March 21, 2004 5:51 PM
Subject: Re: tied hashes frustration
> Ah yes pnotes. You know actually I think you mentioned this once before
in
> a
Ah yes pnotes. You know actually I think you mentioned this once before in
a similar thread I brought up, not sure why I didn't remember it.
> > since some of the methods in my modules are called from the template
toolkit
> > via callbacks, it's really difficult to make sure those methods have
ac
On Sat, 2004-03-20 at 14:41, Chris Ochs wrote:
> Now the problem is that when the application dies
> unexpectedly, the session locking leaves a lock on the session file.
Which Apache::Session subclass are you using? With some of them (i.e.
the database-backed ones) you don't really need to bother
I use apache::session in my application which runs as a handler, and the
session variables are needed by just about every module in the application
(14 modules in all). Now the problem is that when the application dies
unexpectedly, the session locking leaves a lock on the session file.
I have ha
