Gerald Richter wrote:
> > OLD STUFF: redhat 5.2, 2.0.36 kernel, 1.3.6 apache, 1.21 mod_perl,
> > perl 5.005_02, apache session 1.04 and a storable of 0.63, embperl
> 1.2.b10,
> > file system sessions and locking data.
> >
> > NEW STUFF: redhat 5.2, 2.0.36 kernel, 1.3.26 apache, 1.27 mod_perl,
> > perl 5.6.1, apache session 1.54, apache sessionX 2.00b3, storable of
> > 2.05, embperl 1.3.4, file system sessions and locking data..
> >...
>
> >
> > yields the following error message:
> >
> > Storable binary image v56.115 more recent than I am (v2.5)
> at blib/lib/Storable.pm
> > (autosplit into blib/lib/auto/Storable/thaw.al) line 364, <FIL> chunk 1,
> at -e line 1
> >
>
> Did you try to install the old storable into the new Perl? If this works you
> could convert it to some other format (e.g. Data::Dumper), install the new
> storeable and put the session data back.
i did think about doing that. that is where question #1 come in:
1) the sessions keys for the new sessions are twice as long as the
old ones. generally, this is a good thing, but i am concerned that
the old session data will not get read when the cookie is submitted.
will the old sessions get read and reused, read and new ones created,
totally ignored?
after i write down my 100k or so dumps, and bring them back into the new
sessions but still with the short session key, will Apache::Session readup the
key and use the session when the cookie is presented by the browser? if
nobody knows the answer, i'll see if i can create a coiple of sessions and test
this theory.
--
___cliff [EMAIL PROTECTED]http://www.genwax.com/
