Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:53602 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 1713 invoked from network); 27 Jun 2011 16:02:00 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 27 Jun 2011 16:02:00 -0000 Authentication-Results: pb1.pair.com smtp.mail=arraypad@gmail.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=arraypad@gmail.com; sender-id=pass; domainkeys=bad Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.212.42 as permitted sender) DomainKey-Status: bad X-DomainKeys: Ecelerity dk_validate implementing draft-delany-domainkeys-base-01 X-PHP-List-Original-Sender: arraypad@gmail.com X-Host-Fingerprint: 209.85.212.42 mail-vw0-f42.google.com Received: from [209.85.212.42] ([209.85.212.42:46645] helo=mail-vw0-f42.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 9E/39-47962-879A80E4 for ; Mon, 27 Jun 2011 12:02:00 -0400 Received: by vwl1 with SMTP id 1so4029988vwl.29 for ; Mon, 27 Jun 2011 09:01:57 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=UN0OQ7S+B0rxqWGksPQ41G6Q5LFptCNvzd09YetEGxw=; b=rcWlabHQSYgYdjZQeUYw5BWAJm+F7/Tkik0Fy6o0PMRhCB1EzBFe2fhAGKk3L7xz9W 2nqTj489WhAafNL75laGXehApoTahDnQ2AXwsVoKT7nwv2UBdrUvSicd/+zuVmUCGhAW 9TaMx4Vdnk0T4WcD68X+YjPHreYp4RL5Za3uw= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=PFGon94vrOE5oovC4kjeAb5vFUybWp6AZA5hYu7oMHU8E4+AZOK1dzZ6bZl1gIZCnm FZV6KhuHFEIRjFzfKutwYXZp1RfZRGzHi7lUKnkDZbdTjGvfXG8oqXR1tlrUVxfWxt00 kuC+y/Ufku/JPWR+TLOmiI+AY0R26eiancsAk= MIME-Version: 1.0 Received: by 10.52.185.8 with SMTP id ey8mr9063857vdc.68.1309190517172; Mon, 27 Jun 2011 09:01:57 -0700 (PDT) Received: by 10.52.107.103 with HTTP; Mon, 27 Jun 2011 09:01:57 -0700 (PDT) In-Reply-To: References: <4E07FE98.9080002@garfieldtech.com> Date: Mon, 27 Jun 2011 17:01:57 +0100 Message-ID: To: Larry Garfield Cc: internals@lists.php.net Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Subject: Re: [PHP-DEV] [RFC] Object oriented session handlers From: arraypad@gmail.com (Arpad Ray) On Mon, Jun 27, 2011 at 5:00 PM, Arpad Ray wrote: > On Mon, Jun 27, 2011 at 4:52 AM, Larry Garfield = wrote: >> I'm a bit confused. =A0If the session handler goes out of its way to ens= ure >> that it's the last thing to run, wouldn't that cause an issue if it trie= s to >> write session data after, say, the database connection object it wants t= o >> use has already been cleaned up? =A0Or is that the use case for the "do = not >> register" parameter? =A0It seems like it would be a fairly common use ca= se... >> > > If the database object isn't manually cleaned up (all references to it > are unset) then that will take place in the second stage of the > request shutdown process, whereas the first stage is running the > shutdown functions, so that shouldn't be an issue. > > The most common use case for the second argument is where the user > already calls session_write_close() (probably in their own shutdown > function) and doesn't reopen it - it's then useless for us to register > and call our shutdown function. > > Regards, > > Arpad > Oops, CCing the list again.