Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:26958 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 15827 invoked by uid 1010); 14 Dec 2006 17:19:44 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 15812 invoked from network); 14 Dec 2006 17:19:44 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 14 Dec 2006 17:19:44 -0000 Authentication-Results: pb1.pair.com smtp.mail=andrei@gravitonic.com; spf=permerror; sender-id=unknown Authentication-Results: pb1.pair.com header.from=andrei@gravitonic.com; sender-id=unknown Received-SPF: error (pb1.pair.com: domain gravitonic.com from 204.11.219.139 cause and error) X-PHP-List-Original-Sender: andrei@gravitonic.com X-Host-Fingerprint: 204.11.219.139 lerdorf.com Linux 2.5 (sometimes 2.4) (4) Received: from [204.11.219.139] ([204.11.219.139:46941] helo=lerdorf.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id FE/EF-04864-FA781854 for ; Thu, 14 Dec 2006 12:19:44 -0500 Received: from [66.228.175.145] (borndress-lm.corp.yahoo.com [66.228.175.145]) (authenticated bits=0) by lerdorf.com (8.13.8/8.13.8/Debian-3) with ESMTP id kBEHJUaY005036; Thu, 14 Dec 2006 09:19:30 -0800 In-Reply-To: <457856E3.2020607@herballure.com> References: <0c60b01d19ec7e242ade31e29120ee27@gravitonic.com> <4577FC87.7090109@hardened-php.net> <79.1E.13900.F8038754@pb1.pair.com> <5D89A1AE-2EB0-4977-A7EE-B511A4843D27@prohost.org> <45783A9E.3000804@hardened-php.net> <457856E3.2020607@herballure.com> Mime-Version: 1.0 (Apple Message framework v624) Content-Type: text/plain; charset=US-ASCII; format=flowed Message-ID: Content-Transfer-Encoding: 7bit Cc: internals@lists.php.net Date: Thu, 14 Dec 2006 09:19:44 -0800 To: Chad Daelhousen X-Mailer: Apple Mail (2.624) Subject: Re: [PHP-DEV] PHP 5.2: Serialization patch From: andrei@gravitonic.com (Andrei Zmievski) I think 'v' with version info makes sense if we foresee multiple serialization format changes in the future. The steps mentioned below do not seem particularly practical for that reason. I would rather go with a new type 'S' for escaped binary strings in both 6.0 and 5.2.1. -Andrei On Dec 7, 2006, at 10:01 AM, Chad Daelhousen wrote: > As 6.0 is not, to my knowledge, anywhere near release, what about this: > 1. Stick a version number on the front of PHP6-serialized strings. BC > can't break inside the 6.x family if there's nothing to be > compatible with. > 2. Don't change serialize() at all in PHP < 6.0.0. No version number, > no > extra escaping. > 3. Add some mechanism to tell PHP6 to generate a PHP5-compatible binary > string when serializing. I recommend an optional flag (or flags field) > to serialize(). > 4. Understand the new version number in PHP 5.2.1+. > > That would not touch existing serialization format. It would keep > existing compatibility among the 4.x and 5.x family, and allow future > PHPs to unambiguously determine how to parse the string. With the > serialize() flag, you could explicitly generate old-style data from > PHP6 > if you really, really wanted to pass it back to PHP 5.2.0 or earlier. > > -- > Chad Daelhousen > "Television shepherds with living room sheep/ And I pray" > --Temple of the Dog, "Wooden Jesus" > > -- > PHP Internals - PHP Runtime Development Mailing List > To unsubscribe, visit: http://www.php.net/unsub.php