Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:92168 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 18845 invoked from network); 8 Apr 2016 09:39:52 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 8 Apr 2016 09:39:52 -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.66 as permitted sender) X-PHP-List-Original-Sender: yohgaki@gmail.com X-Host-Fingerprint: 209.85.213.66 mail-vk0-f66.google.com Received: from [209.85.213.66] ([209.85.213.66:32847] helo=mail-vk0-f66.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id B9/15-25122-76C77075 for ; Fri, 08 Apr 2016 05:39:51 -0400 Received: by mail-vk0-f66.google.com with SMTP id v68so15544375vka.0 for ; Fri, 08 Apr 2016 02:39:51 -0700 (PDT) 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; bh=ZptSmuFGRnu4auBsuonfK+YHMpF0rbbXAu6kkH86yOQ=; b=GqDz2g3+J5S7YmtxpezElR0F8Lr/FPddW43e/74x7+UNQHw3kqTF8LNgvt28g1OUeo hlM7GpcyvvmE4lnVjSVZ1Bu/xJ6/vRZre3CPRTDe7kF3pl13t/IalAk7ku1gE4BXX0Fw Ny6XFwmdy4ekxGl7Dloyj28ctL6oHh8XsoO3e54hGN5d8chkKlUTDBAdI80NFI8qQIxR ytdKhxkenHKhwUGkOWXqUBIoQgmBEzQ5rD6eYluDfoGHEkxdt4li6FhWhO/Fo19ZHOYO Fi+EDlAmbvmDbmFIC/mzDW3ehGrgqWGXKSaZBzFlx+RLyHuLfOVUGBXVjB+8VLXre1nr LNSw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=ZptSmuFGRnu4auBsuonfK+YHMpF0rbbXAu6kkH86yOQ=; b=Sr4rE/48Tq0NEfV/+qmMg5+ZnqnV+O1rLgOKE2GnSQuBk40oeIal52xDBKx4496edg 3OyF+Mgk8dyt9C/x7OpL7qkE+KGt09UPUXcTfMQ3WdYp52OtreXHVHTvrBEHhCJO5YSI IQ+s2W/pqcR6/Wedl+1iqTQbNd81C8ttdNReeZZIh7dDEkzyIeLm8WoGNAmWQO5NqxP1 gua95a6aZFkKswgncAYqeY3qUDa2fKlF6flVLuwDBo1ftUwIkcCLzPm/SCZuxvL85hef 0sKwEXtMWO6AONshUZ9oHBFCu75L4wqmrBdZ7P31g48J+/GTbJJPNWZFEtHSEvH0JWpw uThg== X-Gm-Message-State: AD7BkJIkgh5Tv7/CTJjg9URTBDYPb48/ko+b2XWbhlh5crqhWjK72adPDwruX7tcsQ7qfb98sHq09bjmSsli9w== X-Received: by 10.159.37.181 with SMTP id 50mr3667223uaf.2.1460108389124; Fri, 08 Apr 2016 02:39:49 -0700 (PDT) MIME-Version: 1.0 Sender: yohgaki@gmail.com Received: by 10.159.40.7 with HTTP; Fri, 8 Apr 2016 02:39:09 -0700 (PDT) In-Reply-To: References: Date: Fri, 8 Apr 2016 18:39:09 +0900 X-Google-Sender-Auth: yC5Cyj3dk-WItg0FkWY1ptNPMJ4 Message-ID: To: Andrey Andreev Cc: "internals@lists.php.net" Content-Type: text/plain; charset=UTF-8 Subject: Re: [PHP-DEV] [RFC][Discussion] Add session_gc() From: yohgaki@ohgaki.net (Yasuo Ohgaki) Hi Andrey, On Fri, Apr 8, 2016 at 6:24 PM, Andrey Andreev wrote: > On Fri, Apr 8, 2016 at 11:38 AM, Yasuo Ohgaki wrote: >> >> Hi Andrey, >> >> On Fri, Apr 8, 2016 at 5:02 PM, Andrey Andreev wrote: >> > On Fri, Apr 8, 2016 at 6:46 AM, Yasuo Ohgaki wrote: >> >> >> >> ,,, >> >> >> >> > >> >> > Speaking of the documentation part - it's not hard to imagine A LOT >> >> > of >> >> > people doing this: >> >> > >> >> > session_start(); >> >> > session_gc(); >> >> > >> >> > That's not a small problem. >> >> >> >> Shooting their own foot is not our problem, but leaving obsolete and >> >> possibly active session is ours. >> >> >> > >> > If you want to explicitly document something as a best practice, it IS >> > your >> > problem when users shoot their feet with it >> >> Lack of proper API for required task is our problem. Misuse is not ours. >> IMHO. > > > I understand your POV, but you can't advertise something as a best practice > and not warn about mistakes that are easy to make - it would be indecent at > the very least. We were getting bug reports like "Calling save handler function directly crashes PHP". Many of crash bugs by misuse are fixed, but we have to consider such misuses also. We also have to consider service providers. They should be able to use session_gc() properly and mitigate risk of obsolete session being active again. Regards, -- Yasuo Ohgaki yohgaki@ohgaki.net