hi!
now I take some time to analyze and test. it's not the problem about
session or cookies.
I init my %session in a module (lets say config.pm).
every app uses a correct (different to the other) path to their module
with different init data.
in app a:
use lib "/var/www/a";
use config;
config->init ();
and in app b:
use lib "/var/www/b";
use config;
config->init ();
so it happens, that a goes into init from b and the opposite. therefore
I got bad session data.
why??? any ideas?
if I rename config to configa and configb and use it in a and b it will
go fine.
thanks
chris
ch wrote:
> hi!
>
> I use different sids in my masonhandler:
>
> my $sid = "SID-A"; # other is SID-B in my 2. masonhandler
> my %session;
> tie %session, "Apache::Session::File", ( $cookies {$sid} ? $cookies
> {$sid}->value () : undef), {};
>
>
> The info in the browser about the cookie tells my that the names are
> my $sid and so it is different. but the path ans host is the same ("/").
>
> hmmm....
>
>
> thanks
> chris
>
>
>
>
>
>
>
------------------------------------------------------------------------------
This SF.Net email is sponsored by the Verizon Developer Community
Take advantage of Verizon's best-in-class app development support
A streamlined, 14 day to market process makes app distribution fast and easy
Join now and get one step closer to millions of Verizon customers
http://p.sf.net/sfu/verizon-dev2dev
_______________________________________________
Mason-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mason-users
