Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:81079 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 68617 invoked from network); 24 Jan 2015 16:21:13 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 24 Jan 2015 16:21:13 -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.192.42 as permitted sender) X-PHP-List-Original-Sender: yohgaki@gmail.com X-Host-Fingerprint: 209.85.192.42 mail-qg0-f42.google.com Received: from [209.85.192.42] ([209.85.192.42:55011] helo=mail-qg0-f42.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 3E/B2-49997-576C3C45 for ; Sat, 24 Jan 2015 11:21:11 -0500 Received: by mail-qg0-f42.google.com with SMTP id q107so1956715qgd.1 for ; Sat, 24 Jan 2015 08:21:06 -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=QLh6n6R+gge+CRBgzl1p4b6ejokTaJuad+1+OfhccIQ=; b=QYPz0boZvjFdhbUtDOjLHKK8e5wsFXbfkDoyXr+ktNbQUIz+W2dng/PmJSbg+AKG33 oT6YP5B3uLIDZ+M+cyeGocF5iaDlpCfhGIMrtVKwwFyhixsbWrAgrfxrBcJ0ctGpzzY5 jFha088nHUpBruC0+BBvShKLTcah+lzKWZTEUQIKRzXjSCqQZGYcw17riNYem6hYXlp5 vaDqKenJThTcgp19NoRRSI/FW7HcJm6ULo2PFvubRY+Ba4TCd7iyehTo2impYKwLAeQ1 Q0rEVcsuWofbqkfonDPdO1ch6T3GKPpJ2cABGTRIoixQDyHazWqh1aZGuWqlOR+9FTz3 M+tw== X-Received: by 10.224.111.194 with SMTP id t2mr20125655qap.86.1422116466619; Sat, 24 Jan 2015 08:21:06 -0800 (PST) MIME-Version: 1.0 Sender: yohgaki@gmail.com Received: by 10.229.93.70 with HTTP; Sat, 24 Jan 2015 08:20:26 -0800 (PST) In-Reply-To: References: <20150124034522.7F51C2615F8@dd15934.kasserver.com> Date: Sun, 25 Jan 2015 01:20:26 +0900 X-Google-Sender-Auth: cb4T5DAIF7q1CnLneGegxsTU9oE Message-ID: To: Rowan Collins Cc: Thomas Bley , "internals@lists.php.net" Content-Type: multipart/alternative; boundary=047d7b604582d27f57050d684a01 Subject: Re: [PHP-DEV] User defined session serialize handler From: yohgaki@ohgaki.net (Yasuo Ohgaki) --047d7b604582d27f57050d684a01 Content-Type: text/plain; charset=UTF-8 Hi Rowan, On Sun, Jan 25, 2015 at 12:35 AM, Rowan Collins wrote: > On 24 January 2015 03:45:22 GMT, Thomas Bley wrote: > >Sessions take a big amount of data in production systems, so it might > >be worth to use msgpack (or others) as an option. > > This came up before, and it was pointed out that a fast implementation of > something like msgpack would need to be implemented as an extension anyway, > not userspace code. And extensions can already register a serialisation > handler, so do not need a userspace callback; I believe igbinary implements > this, for instance. I agree that fast serializer should be implemented by native code. 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 cannot write all possible serialize handlers users want. Therefore, I would like to introduce user serialize handler. Regards, -- Yasuo Ohgaki yohgaki@ohgaki.net --047d7b604582d27f57050d684a01--