Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:53053 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 25785 invoked from network); 6 Jun 2011 17:02:01 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 6 Jun 2011 17:02:01 -0000 Authentication-Results: pb1.pair.com header.from=pencap@gmail.com; sender-id=pass; domainkeys=bad Authentication-Results: pb1.pair.com smtp.mail=pencap@gmail.com; spf=pass; sender-id=pass 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: pencap@gmail.com X-Host-Fingerprint: 209.85.212.42 mail-vw0-f42.google.com Received: from [209.85.212.42] ([209.85.212.42:41649] helo=mail-vw0-f42.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 8A/E5-23189-7080DED4 for ; Mon, 06 Jun 2011 13:02:00 -0400 Received: by vwl1 with SMTP id 1so3309107vwl.29 for ; Mon, 06 Jun 2011 10:00:51 -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:content-type; bh=jfDs/MH1+auNK0zcVYTWYP7h7tbKC1V6qZBatR6xkN8=; b=birUkgYBsBE5UilKSga7g6lr8cJz4czFH21ujJuoSh7v9d6TAJmcDZN2ZQn4FftDSN E1Y7W2pS9UYtVf9DGLwSLvwYVaQfxlQSFAVLUDZxVePSA21U+su1NCWl6EK+i5lzYDr1 nE9f1/Y3Bqi4jXyC4231193tdfYTrGyG5mPlA= 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 :content-type; b=ZTWFGRCXGW8i4F4ZcQ0XOWOL8nAmyTEHNBoyvFkwmyyRGYpUWbx4a9kjhvvZL03lNN mv+iEnOuQogVJ7sPb7TOFZkmReog8R22CUxGL/TRc+2jTO+U2V+7p2FBJGALAM4IKKv3 BcnEuBIiOA4PoxsDS0yEdh9UX3Cr8qS0m7Xdc= MIME-Version: 1.0 Received: by 10.52.109.228 with SMTP id hv4mr2527692vdb.42.1307379651607; Mon, 06 Jun 2011 10:00:51 -0700 (PDT) Received: by 10.52.186.68 with HTTP; Mon, 6 Jun 2011 10:00:51 -0700 (PDT) In-Reply-To: References: Date: Mon, 6 Jun 2011 12:00:51 -0500 Message-ID: To: PHP Internals Content-Type: multipart/alternative; boundary=bcaec5486088b87db804a50e0b83 Subject: Re: [PHP-DEV] [RFC] Object oriented session handlers From: pencap@gmail.com (Mike Willbanks) --bcaec5486088b87db804a50e0b83 Content-Type: text/plain; charset=UTF-8 Forgot to keep the list on this one. On Mon, Jun 6, 2011 at 11:19 AM, Mike Willbanks wrote: > A while ago I submitted a patch to allow session_set_save_handler() to >> accept a class, and support the inheritance of the default session >> handler's methods. >> >> The RFC has a more detailed description and the current patch: >> https://wiki.php.net/rfc/session-oo >> >> Changes since this was last discussed: >> - More sanity checking to prevent handlers being called in unexpected >> states >> - ZTS fixes >> >> Any thoughts? >> > > Unfortunately the class may cause a BC break due to the naming. Although > namespaces could help in reducing the potential scope of a BC break. > > This is a huge win for those of us with generally highly custom session > handlers. This has been a consistent point of pain and being able to > "extend" rather than reimplement would be a very nice enhancement. > > Now on the new SessionHandler object; is this now utilized by default? I > seen the wrapper in the patch but it seems like we utilize all of the > existing code with modifications to also utilize an object? Should > the procedural way be deprecated at some point or is the plan to support > both styles? > > Regards, > > Mike > > --bcaec5486088b87db804a50e0b83--