Dave Rolsky wrote:
> On Mon, 17 Oct 2005, Perrin Harkins wrote:
>
>> On Mon, 2005-10-17 at 11:46 -0400, Tom Daly wrote:
>>>> $m->comp("REQUEST:$mode", %ARGS, state => $Session{$state_var});
>>
>> I'm just guessing, but maybe things that get passed as comp() params are
>> persistent for some reason. Maybe you should try making the session
>> available in a different way, like having a singleton object.
>
> They really shouldn't be, so if they are it's certainly a bug.
Did anyone find a solution to this? I just ran into the same problem and spent
several hours trying to work out what was going on. It definitely seems to be
related to the comp() call.
Weirdly the only thing that seemed to work was setting the args to undef at
the end of the called component:
% map {$ARGS{$_}=undef;} keys %ARGS;
simply deleting them from the ARGS hash didn't work, using an <%args> block
and unsetting each one individually also works.
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Mason-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mason-users
