Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:71309 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 25834 invoked from network); 20 Jan 2014 08:43:25 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 20 Jan 2014 08:43:25 -0000 Authentication-Results: pb1.pair.com header.from=yohgaki@gmail.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=yohgaki@gmail.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.215.43 as permitted sender) X-PHP-List-Original-Sender: yohgaki@gmail.com X-Host-Fingerprint: 209.85.215.43 mail-la0-f43.google.com Received: from [209.85.215.43] ([209.85.215.43:34953] helo=mail-la0-f43.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id FA/C4-02192-BA1ECD25 for ; Mon, 20 Jan 2014 03:43:24 -0500 Received: by mail-la0-f43.google.com with SMTP id er20so5301236lab.16 for ; Mon, 20 Jan 2014 00:43:20 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc:content-type; bh=BsKq0CDZp4P/tOSi1ezq75dCN5iVQnaCIhfUG3a3nTE=; b=jQ3YRm9+liRVaeGHj8EKveN5s8tmqUHoUfKiFxTF/mrweLnEhtzqVX5nMxr5p5vSI1 wgd+mcRVoWk/P80Q8VKMwodccsCvMGVtvnBQWCVn9nJ6AJp00VlKWoEloSY3hTnuv4pv NwBRP6+LBgqIjt5YOPX1RcFNOZCEThxp0MVpPQCEsa1l9oOZSPHlXgNOP0dzsx6qpNCH KUEdai3fsZRGTg2JJIdnBdeJuSgL0OOHf9lEfn6b4JeHsxrkedZeDXuDxSxrf1URDK5r DiKhTnZW4KXfNqZqSUgIXkFNrf9mX9NJ5nPuUGTkn1nziDd/WGqxL5V/Ikh3a1B6xhkD wJgQ== X-Received: by 10.112.138.233 with SMTP id qt9mr926736lbb.34.1390207399977; Mon, 20 Jan 2014 00:43:19 -0800 (PST) MIME-Version: 1.0 Sender: yohgaki@gmail.com Received: by 10.112.6.68 with HTTP; Mon, 20 Jan 2014 00:42:38 -0800 (PST) In-Reply-To: <52DCDDDB.70000@tobin.nl> References: <52DCDDDB.70000@tobin.nl> Date: Mon, 20 Jan 2014 17:42:38 +0900 X-Google-Sender-Auth: vuvRQ37yFswMpML3I5vkVqS1fbc Message-ID: To: Bas van Beek Cc: "internals@lists.php.net" Content-Type: multipart/alternative; boundary=089e012297103d699204f062e2a0 Subject: Re: [PHP-DEV] [VOTE] Introduce session.lock, session.lazy_write and session.lazy_destory From: yohgaki@ohgaki.net (Yasuo Ohgaki) --089e012297103d699204f062e2a0 Content-Type: text/plain; charset=UTF-8 Hi Bas, On Mon, Jan 20, 2014 at 5:27 PM, Bas van Beek wrote: > I see only one very simple function potentially being helpful. A simple > session close without write maybe called session_close(). This would give > a performance bonus as it will not need to serialize the session data and > write it back to session storage. It also helps to programmer in cases > that he wants to guarantee that the session store is not changed by > script (similar to a transaction abort). > I have already added this as session_abort(). Since it's only in 5.6 and master branch, the name could be changed. However, session_abort() (or something like session_discard()) would be better name because the name implies it does not save data. If you come up with better name, please let me know. Regards, -- Yasuo Ohgaki yohgaki@ohgaki.net --089e012297103d699204f062e2a0--