Josh,
Thank you for your insite into our problem. We have some more
ammunition to play with now.
> > 2) How might we speed this process up or are we heading down
blind
> > alley?
> >
>
> Try SessionSerialize setting, similar to calling $Session->Lock in
the
> Script_OnStart. Try not accessing keys too often. You might try to
> make a read only copy of data like this:
>
> use vars qw($SessionReadOnly);
> sub Script_OnStart {
> $SessionReadOnly = { %$Session };
> }
>
> so if you are accessing same data multiple times, this might be
faster.
This brings up another set of questions I have had regarding Session
data. I have tried finding the answer in posts/docs/etc. but haven't
found a definitive answer.
How does a series of reads or writes to a Session object hit the disk
and the StateSerializer?
For instance, let's say I did this:
$Session->{'key1'}=data1
$Session->{'key2'}=data2
$Session->{'key3'}=data3
or
data1=$Session->{'key1'}
data2=$Session->{'key2'}
data3=$Session->{'key3'}
Does each statement cause a freeze/thaw of the whole Session data
structure to/from disk?
In your code, you make one read only copy. Does this cause only one
thaw? This is why your proposed trick would help, right?
Cheers,
Christian
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
