Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:99666 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 71572 invoked from network); 28 Jun 2017 23:13:00 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 28 Jun 2017 23:13:00 -0000 Authentication-Results: pb1.pair.com smtp.mail=smalyshev@gmail.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=smalyshev@gmail.com; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.83.54 as permitted sender) X-PHP-List-Original-Sender: smalyshev@gmail.com X-Host-Fingerprint: 74.125.83.54 mail-pg0-f54.google.com Received: from [74.125.83.54] ([74.125.83.54:33844] helo=mail-pg0-f54.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id E6/C5-07609-AF734595 for ; Wed, 28 Jun 2017 19:13:00 -0400 Received: by mail-pg0-f54.google.com with SMTP id t186so38800838pgb.1 for ; Wed, 28 Jun 2017 16:12:58 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-language:content-transfer-encoding; bh=LXtxFscSyaxW0FvPg3O2njhFTnMDenHQtZHKhzhyQ+0=; b=VrruzZtpThv6XdSepf/0fKxnbmbvh+H3d8gbN5e/0FcteTh6TW45pEe6A5xgnp4sIg Yl3R6jWkH5wXO/QO22KQ4T/HwDBRcsqEfSCH/NNv0nT9h9IejefGfur6IVTv/FGYwinT kCRex7N+xGZ7001UeZk/V3x4U/JKznT0AYwg+JkhCU/ZGxujahDgdrOxh54yF0td8vVa wY+40aNZUH7PTTF39bzB//YJfJ9tw/qiKUMSSpiaqv8jCUEBoRFs8BySe26Fa0YUQGTm oR0FbFKL3iRmkZLN3+uL46/ta7so1QxtrTwv8goORQ5Jqn7mkzjeiU4OHFD8Fck4aJby u2WQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=LXtxFscSyaxW0FvPg3O2njhFTnMDenHQtZHKhzhyQ+0=; b=jo5F5I86P7gH9jAtbF1EssIEdbtSQNtCsStggo9llGPenN4oy/Dyz9tJi5oRZhxJWn CIKfIRhkzmE475qcfbJQhVFMCyOr+67d/7ccNnBdToLlCbGnm+Uou7wLw496WpKVQrX7 1eKdokZoQvQCxGzLx3mkezMgzoDfPW7qx9P19m0QgmJfdVrGgDTE5LII5G6Lp+r3ES89 STES5ilS/S14ZngsOToP63+IR8oi6Mp8G/BvzmyUrOGJtk7iAHmElwbhKMz7qb+qW3NO WcAC73REC3MtwSY6MwHFUXidQ3X0WHFDmt26JUXuaNmNioB/IhQwXsnkqfbdcAuZFMAD BAag== X-Gm-Message-State: AKS2vOwmpdFUkQl0r2OpEreLo0VkRlnhm4Ne44gzvm4SYy6ijuTMyhPI 37uzslZDcyDImMAHWNk= X-Received: by 10.99.2.134 with SMTP id 128mr12889799pgc.266.1498691575655; Wed, 28 Jun 2017 16:12:55 -0700 (PDT) Received: from Stas-Air.lan (108-233-206-104.lightspeed.sntcca.sbcglobal.net. [108.233.206.104]) by smtp.gmail.com with ESMTPSA id s7sm5591149pgb.53.2017.06.28.16.12.54 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 28 Jun 2017 16:12:54 -0700 (PDT) To: Rasmus Schultz , PHP internals References: Message-ID: <831f345f-6d6a-9d9b-e691-c92c49cfefed@gmail.com> Date: Wed, 28 Jun 2017 16:13:20 -0700 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:52.0) Gecko/20100101 Thunderbird/52.2.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] Binary (msgpack) serialize/unserialize From: smalyshev@gmail.com (Stanislav Malyshev) Hi! > Back in 2014 there was an informal proposal on the mailing list to replace > PHP serialization with an efficient binary (msgpack) format. Why replace? If you have it as an extension, can't people that want to use it just use it? I'm still not sure why we need to do anything in core that can't be done in an extension. Is there some handler missing that doesn't allow to use custom serializer in some scenario? -- Stas Malyshev smalyshev@gmail.com