RE: Apache::Session - kludgy workaround?

[Jeffrey W. Baker]

On Wed, 4 Oct 2000, Jerrad Pierce wrote:

> Reading the directions ;-)
> 
> Apache::Session doesn't do any deep checking, if a top level doesn't value
> doesn't change
> it may not detect the change.
> 
> This is why your workaround works...
> 
> The offically recommend workaround (I believe) is to keep a timestamp as a
> top level value in the hash...

You may also force saving of a session via:

tied(%session)->make_modified();

There is a complete object interface to Apache::Session but you have to
read Session.pm to explore it.

-jwb

RE: Apache::Session - kludgy workaround?

[Jerrad Pierce]

Reading the directions ;-)

Apache::Session doesn't do any deep checking, if a top level doesn't value
doesn't change
it may not detect the change.

This is why your workaround works...

The offically recommend workaround (I believe) is to keep a timestamp as a
top level value in the hash...

>-Original Message-
>From: Ian Mahuron [mailto:[EMAIL PROTECTED]]
>Sent: Wednesday, October 04, 2000 2:48 PM
>To: ml: mod_perl
>Subject: Apache::Session - kludgy workaround?
>
>
>
>If I repeatedly write to:
>
>$session{foo}{bar}
>
>I find that I have to do something like:
>
>$session{smack}++;
>
>to get it to write when the hash is untied.  Is there a better 
>way to do this?
>
>TIA
>
>ian
>