Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:78770 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 47432 invoked from network); 6 Nov 2014 02:03:31 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 6 Nov 2014 02:03:31 -0000 Authentication-Results: pb1.pair.com smtp.mail=yohgaki@gmail.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=yohgaki@gmail.com; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.213.172 as permitted sender) X-PHP-List-Original-Sender: yohgaki@gmail.com X-Host-Fingerprint: 209.85.213.172 mail-ig0-f172.google.com Received: from [209.85.213.172] ([209.85.213.172:56471] helo=mail-ig0-f172.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id D2/93-28384-2F6DA545 for ; Wed, 05 Nov 2014 21:03:31 -0500 Received: by mail-ig0-f172.google.com with SMTP id a13so9915256igq.11 for ; Wed, 05 Nov 2014 18:03:28 -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=sZ/3NfOxNdK3f7GF67gAh0iLK9qh/gl4xk59k58a/X4=; b=C6LjCR6By7mQuVi467eU8l+nBBbjthD0a6FHQ2PmvW2EnlZUBOgZN7kNfcGAFA0G0h 3KV+TAWP7eeFHgzSI5HYrVLZhDkmwXCAe87gJ9tFEhx8VO9rX7f2UfOg3/aDlfFN09Xf O/ClL0TgQGJFEXfMfFoxInFL9dxeMbT8Q1nhPdjFTu3fBGsExrHiCDiJbrMBYcuRN9ZN O6DoV9JVDptqdHRuUuBedXOcEtYKd6IO18j9v2wZTnOUtrn1xvrA1aCsKSRln92qB7zk +SXzjNv8vMgW4E9T0RLC/NKst0Cl9H+3NiLFvrGMJMqRdxXIGpsVCs0BdBZN9SDlOpyH F3pg== X-Received: by 10.43.140.198 with SMTP id jb6mr8398138icc.34.1415239408132; Wed, 05 Nov 2014 18:03:28 -0800 (PST) MIME-Version: 1.0 Sender: yohgaki@gmail.com Received: by 10.107.132.216 with HTTP; Wed, 5 Nov 2014 18:02:47 -0800 (PST) In-Reply-To: References: Date: Thu, 6 Nov 2014 11:02:47 +0900 X-Google-Sender-Auth: WRsCDWxpKdl8KAZRCsOENq0PaHM Message-ID: To: Damian Wadley Cc: PHP internals Content-Type: multipart/alternative; boundary=001a11c326fe31abd00507271a47 Subject: Re: [PHP-DEV] Lazy writing in the session, session-lock-ini, and bug #68331 From: yohgaki@ohgaki.net (Yasuo Ohgaki) --001a11c326fe31abd00507271a47 Content-Type: text/plain; charset=UTF-8 HI all, On Thu, Nov 6, 2014 at 6:30 AM, Yasuo Ohgaki wrote: > On Wed, Nov 5, 2014 at 10:54 AM, Damian Wadley wrote: > >> Apparently this caused >> problems for some people as they made 68331 a few days ago. >> > > Just a quick note for this. The user would like to access session > data(session handler) > regardless of data modification. I suppose it could be solved if session > has user space > "update" handler as I suggested originally. > > Alternatively, session_write_close()/session_commit() may be changed, so > that it > is called unconditionally during shutdown. I have to read the code to be > sure if this is possible. > > BTW, anyone know the reason why the user need to call > session_write_close()/session_commit() > unconditionally? Accounting, perhaps? > The issue user has reported could be solved easily by calling write API during shutdown, IIRC. An explicit flag for this might be needed. I'm just curious for what reason the user needs to call session_write_close() during shutdown. It could be used as user states in old PHP, but it does not make it valid usage/design automatically, so I wander the reason. Regards, -- Yasuo Ohgaki yohgaki@ohgaki.net --001a11c326fe31abd00507271a47--