Return-Path: Delivered-To: apmail-perl-embperl-archive@perl.apache.org Received: (qmail 32124 invoked by uid 500); 15 Oct 2002 01:00:46 -0000 Mailing-List: contact embperl-help@perl.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Delivered-To: mailing list embperl@perl.apache.org Received: (qmail 32107 invoked from network); 15 Oct 2002 01:00:45 -0000 Mime-Version: 1.0 X-Sender: nazgul@somewhere.com@puremessaging.com (Unverified) Message-Id: Date: Sat, 12 Oct 2002 14:44:51 -0400 To: embperl@perl.apache.org From: Kee Hinckley Subject: Quick udat clarification Content-Type: text/plain; charset="us-ascii" ; format="flowed" X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N 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 I'm trying to make sure that my site doesn't gratuitously create cookies until there's actually something that the user wants us to remember. -- 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