Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:70138 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 73031 invoked from network); 14 Nov 2013 21:57:32 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 14 Nov 2013 21:57:32 -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.49 as permitted sender) X-PHP-List-Original-Sender: yohgaki@gmail.com X-Host-Fingerprint: 209.85.215.49 mail-la0-f49.google.com Received: from [209.85.215.49] ([209.85.215.49:46700] helo=mail-la0-f49.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 6D/54-53459-B4745825 for ; Thu, 14 Nov 2013 16:57:31 -0500 Received: by mail-la0-f49.google.com with SMTP id er20so2070868lab.22 for ; Thu, 14 Nov 2013 13:57: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=5OhRafKIj5PTw/MF4R7syCewBrCCXZdcADqHpN1QBag=; b=DtBh/fY3X1cOsB5idWWbkZj8PxBWvFH5mEviQSuy0B9zQ2DQWtmHbjU3L/lVIUb02P VhNcat+q3myZsIuyMuKpx106y/mli8zAX9Xpm7+mh+c29GITgRjGwXSRntgtsDrRPQkg 1YRKicSzzpKuocW+H02VbipFOLspYUG9SnEeesJucwylHTXPGuzciDK8UHu9VGXQ9UU4 pTOAirvmYjGJxRzgOmDm7FIKIb4THa7QUQoX9d7+seGUogLl0OrPIWZqPiesWrB+qKLs F8dIU+ttLDR5Yq/V0YbIMEXDfXrfT6kr4ZN27AjLLBiCgvorM1fHsxSN8pfvU2rv/k5f Hldw== X-Received: by 10.112.159.231 with SMTP id xf7mr1970993lbb.18.1384466248202; Thu, 14 Nov 2013 13:57:28 -0800 (PST) MIME-Version: 1.0 Sender: yohgaki@gmail.com Received: by 10.112.154.201 with HTTP; Thu, 14 Nov 2013 13:56:48 -0800 (PST) In-Reply-To: References: Date: Fri, 15 Nov 2013 06:56:48 +0900 X-Google-Sender-Auth: 81NPDsKY4R0JvB7lLpaXauvzpp4 Message-ID: To: Adam Harvey Cc: "internals@lists.php.net" Content-Type: multipart/alternative; boundary=001a11c3c4feedbb0104eb2a2a6b Subject: Re: [PHP-DEV] Session cache, lock and write From: yohgaki@ohgaki.net (Yasuo Ohgaki) --001a11c3c4feedbb0104eb2a2a6b Content-Type: text/plain; charset=UTF-8 Hi Adam, On Fri, Nov 15, 2013 at 5:29 AM, Yasuo Ohgaki wrote: > I wonder if a better approach would be to implement an improved files >> handler (under a different name) that had options for locking, caching >> and the like. Say it was called "awesome_files"[0]; you might have >> options like this: >> >> session.save_handler = awesome_files >> session.awesome_files.lock = On/Off >> >> I'd love to have a more flexible files handler, but I don't think we >> want to overspecialise the session implementation around it. > > > The behavior can be controlled by setting, so I would like to keep > single code files/mm/user and other save handlers. > > I don't mind creating new handlers too much, but I'm concerned for having > multiple settings for each save handlers. (e.g. Memcached/MongoDB save > handler have it own lock setting. It would be better to have single setting > for any save handlers that support it.) > It seems we need to think of new files save handler name. Perhaps, "files_ext"? Any better names? Regards, -- Yasuo Ohgaki yohgaki@ohgaki.net --001a11c3c4feedbb0104eb2a2a6b--