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
