Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:73444 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 6343 invoked from network); 26 Mar 2014 11:15:48 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 26 Mar 2014 11:15:48 -0000 Authentication-Results: pb1.pair.com header.from=narf@devilix.net; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=narf@devilix.net; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain devilix.net designates 209.85.160.175 as permitted sender) X-PHP-List-Original-Sender: narf@devilix.net X-Host-Fingerprint: 209.85.160.175 mail-yk0-f175.google.com Received: from [209.85.160.175] ([209.85.160.175:57848] helo=mail-yk0-f175.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id EF/E0-33864-3E6B2335 for ; Wed, 26 Mar 2014 06:15:48 -0500 Received: by mail-yk0-f175.google.com with SMTP id 131so528292ykp.34 for ; Wed, 26 Mar 2014 04:15:44 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=devilix.net; s=google; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=2Lqqpdb7WPergfdngg6FyJDqDBtMuXv8ZJi3O61es2c=; b=CUT6u6flWrDncxwT19BU6d1SGiq5JWB88vDM9GeyiYayP46O3iF2KJ9+t5hHSCZQ8t E774hdKvsmNfkkzhaLfwMdSN6l3z8hcPLzzuMxeSAwuSFRKxSub3p724oWIeAbCZdNYm F93WuDMQDoDs11YUX/ICnDVQb9OVMNidjhRIk= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=2Lqqpdb7WPergfdngg6FyJDqDBtMuXv8ZJi3O61es2c=; b=XeuswFmGFS9ejWuClCfmkJZXQK74FP3mHsF07baJF4e5mykMlobMK3gVqStHxJSCm0 wAAon3/67VfUogSRTGXFfxESfPwlEFDY/OnjNXgSU0CF9gQCeSOWMdXVIpUuelgFKAn/ ZrwkO55ObpySBKqsioSJpK0kFNLDZ1m0euG31wFTQHEsdqdPR5OmnQHnWDz0BW8nLNyI /e+IiKD9QJqLJel1juZ1FY7cuyoFKPcp6xHwNEJP9V04jtKUcDrQAAj970zZFS/kdk4Z YtjLx2KYhaRM51RAABPE6UVsIjTtFIUmlyqkV9AwWjViarZbjXCreYgo4sA94+ElGGld sWLg== X-Gm-Message-State: ALoCoQlzjWrifU7tY6z1BjXC2MSoC2ZLefi+OjFyAfDex7DLitfiaC+WzkDcHmzugRxLLs7eOcBo MIME-Version: 1.0 X-Received: by 10.236.116.131 with SMTP id g3mr9755634yhh.110.1395832544138; Wed, 26 Mar 2014 04:15:44 -0700 (PDT) Received: by 10.170.188.139 with HTTP; Wed, 26 Mar 2014 04:15:44 -0700 (PDT) In-Reply-To: References: <010e01cf4788$05f3c5a0$11db50e0$@devtemple.com> <01c801cf47c0$59acbf20$0d063d60$@devtemple.com> Date: Wed, 26 Mar 2014 13:15:44 +0200 Message-ID: To: Julien Pauli Cc: Bill Salak , "internals@lists.php.net" Content-Type: text/plain; charset=UTF-8 Subject: Re: [PHP-DEV] [RFC] session_start(), read_only, lazy_write; Take 2 From: narf@devilix.net (Andrey Andreev) Hi, On Wed, Mar 26, 2014 at 12:29 PM, Julien Pauli wrote: > For non BC changes etc.. , please, consider that you'll have a big time for > rethinking the whole session module for PHP6 if you want to (and I think > I'll be part of deep discussions here) > So don't bother too much in searching solutions for introducting new > concepts in PHP5.X session module while keeping BC. Keep all those for PHP6. Of course, I've got more ideas for PHP6, but what I'm targeting here are already voted features that could've been designed in a better way. Btw, another argument in merging updateTimestamp() into write() is that userland implementations of it up until now have only been possible by altering write(), so at least some users should be more familiar with that approach. For example: class MySessionHandler extends SessionHandler { public $fingerprint; public function read($session_id) { $session_data = parent::read($session_id); $this->fingerprint = md5($session_data); return $session_data; } public function write($session_id, $session_data) { if ($this->fingerprint === md5($session_data) { return touch(ini_get('session.save_path').'/sess_'.$session_id); } return parent::write($session_id, $session_data); } Cheers, Andrey.