Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:81065 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 14204 invoked from network); 24 Jan 2015 02:28:51 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 24 Jan 2015 02:28:51 -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.48 as permitted sender) X-PHP-List-Original-Sender: yohgaki@gmail.com X-Host-Fingerprint: 209.85.192.48 mail-qg0-f48.google.com Received: from [209.85.192.48] ([209.85.192.48:53424] helo=mail-qg0-f48.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id E8/60-10645-26303C45 for ; Fri, 23 Jan 2015 21:28:51 -0500 Received: by mail-qg0-f48.google.com with SMTP id z60so572503qgd.7 for ; Fri, 23 Jan 2015 18:28:47 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:from:date:message-id:subject:to:content-type; bh=TW9cW9qzZhJUuUMx7oxneiCGN6a86Bytwyngl45Spv4=; b=Nouk5Uw1Iao+jd+pS6bThcds13xqz8BgLSbnWABTOzjIiSge9ad6QyV21+t/rQDswk NtED89wJ6og1fsWz7WBZNDGrvLWYrk9JkyFjGhyjKd7cIuLH1dRZO6aEDt9M01hbeGFs 68Z9xZc+5sofAb+zj57QMugRHe7tjTqFH/SX0CiD8FWpLhNuhSE56meJEJzP5jxQS8r5 YdAh2lxeEvjMEwRilBZGDzI901wq6mXpzZBHT4ByBYU3xrBaMcMrYd2NhaMxJgaqIb5F tPfw9KOF7L+EXrPzT5K1cxxBSBR0MtSDMC+vPZsBPagqYUmfU6ADQrBKY8SnINnueK+5 ft5A== X-Received: by 10.224.2.9 with SMTP id 9mr14482382qah.66.1422066527560; Fri, 23 Jan 2015 18:28:47 -0800 (PST) MIME-Version: 1.0 Sender: yohgaki@gmail.com Received: by 10.229.93.70 with HTTP; Fri, 23 Jan 2015 18:28:07 -0800 (PST) Date: Sat, 24 Jan 2015 11:28:07 +0900 X-Google-Sender-Auth: -YyMWBdekWpy9B4c5snmENx2qqo Message-ID: To: "internals@lists.php.net" Content-Type: multipart/alternative; boundary=001a11c22ccc38ec91050d5caa16 Subject: User defined session serialize handler From: yohgaki@ohgaki.net (Yasuo Ohgaki) --001a11c22ccc38ec91050d5caa16 Content-Type: text/plain; charset=UTF-8 Hi all, Session module has session serializer modules that serializes $_SESSION back and forth. Session serializer module can be defined by user if there is API for it. I would like to propose user defined serialize handler API. The user defined serializer API will have similar API like session_set_save_handler(). bool session_set_save_handler(callable $serialize_callback, callable $unserialize_callback) bool session_set_save_handler(SessionSerializer $serializer); interface SessionSerializer { public string function serialize(array $_SESSION); // Return serialized session data public bool function unserialize(array &$_SESSION, string $session_data); // Initialize $_SESSION by $session_data } php.ini : There is "session.serialize_handler" (Default: php) "user" will be added, but user must use session_set_serialize_handler() just like session_set_save_handler(). I also would like to php_serialize handler as the default serializer and make php/php_binary deprecated. php/php_binary serializers are made to work with register_globals and have many limitations. e.g. Integer key not allowed, key cannot start with number, delimiter chars are invalid and ignored, etc. php_serialize does not have such limitations at all. Thank you for your feedback. Regards, -- Yasuo Ohgaki yohgaki@ohgaki.net --001a11c22ccc38ec91050d5caa16--