Mailing-List: contact embperl-help@perl.apache.org; run by ezmlm
Precedence: bulk
Mime-Version: 1.0
Message-Id: <a0530030db9d320596556@[192.168.1.104]>
In-Reply-To: <00d301c274da$854db4b0$0b0c0b0a@gr.ecos.de>
References: <a05300301b9ce1d3d39e9@[192.168.1.104]>
 <00d301c274da$854db4b0$0b0c0b0a@gr.ecos.de>
Date: Wed, 16 Oct 2002 09:56:04 -0400
To: "Gerald Richter" <richter@ecos.de>
From: Kee Hinckley <nazgul@somewhere.com>
Subject: Re: Quick udat clarification
Cc: <embperl@perl.apache.org>
Content-Type: text/plain; charset="us-ascii" ; format="flowed"

At 8:09 AM +0200 10/16/02, Gerald Richter wrote:
>  > The docs say that so long as you don't touch udat, a session won't be
>>  created.  Then they are more specific and say so long as you don't
>>  *write* to udat one won't be created.  I just want to make sure that
>>  reading udat doesn't cause a cookie to be created (or hit the
>>  database).  I think that's the case, but I just wanted to double
>>  check.  Otherwise I can do what I do when I want to write to udat
>>  only if it already exists:
>>       $session = tied %$udat;
>>       return undef if (!$session);                # I don't think this
>happens
>>       $sessid = $session->getid();
>>       return undef if (!$sessid);                 # Won't create a session
>id
>>
>
>$session->getid() will never create a new session if it not already exists

That I'm clear on.  But will
	$a = $udat{foo};
create a new session?
-- 

Kee Hinckley - Somewhere.Com, LLC
http://consulting.somewhere.com/

I'm not sure which upsets me more: that people are so unwilling to accept
responsibility for their own actions, or that they are so eager to regulate
everyone else's.

---------------------------------------------------------------------
To unsubscribe, e-mail: embperl-unsubscribe@perl.apache.org
For additional commands, e-mail: embperl-help@perl.apache.org