Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:81080 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 70514 invoked from network); 24 Jan 2015 16:36:45 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 24 Jan 2015 16:36:45 -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.192.50 as permitted sender) X-PHP-List-Original-Sender: yohgaki@gmail.com X-Host-Fingerprint: 209.85.192.50 mail-qg0-f50.google.com Received: from [209.85.192.50] ([209.85.192.50:47641] helo=mail-qg0-f50.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id E5/13-49997-C1AC3C45 for ; Sat, 24 Jan 2015 11:36:44 -0500 Received: by mail-qg0-f50.google.com with SMTP id f51so1952934qge.9 for ; Sat, 24 Jan 2015 08:36:41 -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=j6RQd0KYcuL4rbgPVpJj4byJ0N4+JeGcY8cqM7N2FbY=; b=w/QkUBhto1g7mBxnJ9cqCaGg+3sY2/czFaQ6j+0mw/ArpcfaUZNUz2iF0/0y06deye XgHpU5SE+w0lXCsCYGHoQWKsl0yFeOyZW02qPcioJtUlz7oRT+4lKeFuH4Qk016f6Uky lcSAeQOtdZFngfiCHTy5PxWTEDbYLgI1yVUZ0iUoME/JY96RW7YS+NgUMXqX9u87AUmZ 9t+KC2uF5ta5dQV9PMKRfgVBjQW7imNoDcTChCMwMwZoHg10OEY4ohD1LFHHX2uxEg0m CNjF3SGkitU3hrmEchDwHpghT3RvaLgK1DQvho9u5aN36aKz5MaE0S2plCDt/oYQFcO2 ghTQ== X-Received: by 10.140.109.164 with SMTP id l33mr24388046qgf.91.1422117401586; Sat, 24 Jan 2015 08:36:41 -0800 (PST) MIME-Version: 1.0 Sender: yohgaki@gmail.com Received: by 10.229.93.70 with HTTP; Sat, 24 Jan 2015 08:36:01 -0800 (PST) In-Reply-To: References: <20150124034522.7F51C2615F8@dd15934.kasserver.com> Date: Sun, 25 Jan 2015 01:36:01 +0900 X-Google-Sender-Auth: 1yglY3cVQQnCM_ZHWueTsIVfM5U Message-ID: To: Rowan Collins Cc: Thomas Bley , "internals@lists.php.net" Content-Type: multipart/alternative; boundary=001a113a304e8d10f8050d68821b Subject: Re: [PHP-DEV] User defined session serialize handler From: yohgaki@ohgaki.net (Yasuo Ohgaki) --001a113a304e8d10f8050d68821b Content-Type: text/plain; charset=UTF-8 Hi all, On Sun, Jan 25, 2015 at 1:20 AM, Yasuo Ohgaki wrote: > However, once user serialize handler is implemented, overhead of user > serialize handler is calling 2 PHP functions. i.e. serialize/unserialize > functions whatever module provides. Users may compress/encrypt session data > whatever methods also. If user wants serialize/compress/encrypt, 6 PHP > functions calls are required. It would be reasonably fast. User serialize > handler provides much freedom than now I forgot about session_set_serialize_handler() call. So there is an additional PHP function call. Regards, -- Yasuo Ohgaki yohgaki@ohgaki.net --001a113a304e8d10f8050d68821b--