Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:54686 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 66952 invoked from network); 18 Aug 2011 13:25:34 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 18 Aug 2011 13:25:34 -0000 Authentication-Results: pb1.pair.com smtp.mail=arvids.godjuks@gmail.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=arvids.godjuks@gmail.com; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.212.42 as permitted sender) X-PHP-List-Original-Sender: arvids.godjuks@gmail.com X-Host-Fingerprint: 209.85.212.42 mail-vw0-f42.google.com Received: from [209.85.212.42] ([209.85.212.42:44917] helo=mail-vw0-f42.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 70/F2-50449-DC21D4E4 for ; Thu, 18 Aug 2011 09:25:34 -0400 Received: by vwl1 with SMTP id 1so1646504vwl.29 for ; Thu, 18 Aug 2011 06:25:31 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=1Pn6ieJDuOEZ/14I6ZOTG5i2pTPssZFzxjUHP1+3Vps=; b=t2Dwnmk8yyEIFuWkbKUB7/KWqUFAXD6P4Pucw2H7GOWN0v6WkxvUpvzIvdrM9xk1Fr Q3F0Z2+RYc3ZvfIamYn/6itr8ze5ofxnqSHfWNqpNfC18QUHVnzbC9HORutONW3Lf7OI R1fqoYUAgbIAYlVMr9rSvESg3ddl32IdD8NSc= MIME-Version: 1.0 Received: by 10.52.96.106 with SMTP id dr10mr750799vdb.150.1313673931536; Thu, 18 Aug 2011 06:25:31 -0700 (PDT) Received: by 10.52.114.230 with HTTP; Thu, 18 Aug 2011 06:25:31 -0700 (PDT) In-Reply-To: References: Date: Thu, 18 Aug 2011 16:25:31 +0300 Message-ID: To: PHP Internals List Content-Type: text/plain; charset=UTF-8 Subject: Re: [PHP-DEV] Activation of IGBinary serialization extension in 5.4 by default From: arvids.godjuks@gmail.com (Arvids Godjuks) Just add a check on what format is used on read, write with the new format. Deprecate the old format in next version after 5.4 (or drop it at all in 6.0 or whatever the new major version will be). Make a noise about the change (I can do that for the Russian speaking community with ease). It will be transparent. People using serialized caches can just drop them and re-init. People storing data can recode it with ease - just read it and write it back - it will be in new format. Problem solved :)