Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:87459 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 4231 invoked from network); 31 Jul 2015 20:55:23 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 31 Jul 2015 20:55:23 -0000 Authentication-Results: pb1.pair.com header.from=anatol.php@belski.net; sender-id=unknown Authentication-Results: pb1.pair.com smtp.mail=anatol.php@belski.net; spf=permerror; sender-id=unknown Received-SPF: error (pb1.pair.com: domain belski.net from 85.214.73.107 cause and error) X-PHP-List-Original-Sender: anatol.php@belski.net X-Host-Fingerprint: 85.214.73.107 klapt.com Received: from [85.214.73.107] ([85.214.73.107:48294] helo=h1123647.serverkompetenz.net) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id FA/C2-24609-9B0EBB55 for ; Fri, 31 Jul 2015 16:55:21 -0400 Received: by h1123647.serverkompetenz.net (Postfix, from userid 1006) id E187923D6299; Fri, 31 Jul 2015 22:55:17 +0200 (CEST) X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on h1123647.serverkompetenz.net X-Spam-Level: X-Spam-Status: No, score=-2.9 required=2.5 tests=ALL_TRUSTED,BAYES_00, URIBL_BLOCKED autolearn=unavailable version=3.3.2 Received: from w530phpdev (pD9FE8EAF.dip0.t-ipconnect.de [217.254.142.175]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by h1123647.serverkompetenz.net (Postfix) with ESMTPSA id 2E1DA23D6003; Fri, 31 Jul 2015 22:55:15 +0200 (CEST) To: "'Stanislav Malyshev'" , "'Marco Pivetta'" , "'Rowan Collins'" Cc: "'Nikita Popov'" , "'PHP Internals List'" References: <550FA2ED.6080000@gmail.com> <55B7B08E.7070700@gmail.com> <140E45EA-72E6-4CA6-8C03-6DBDB3E81D5E@gmail.com> <55B7EB30.9020008@gmail.com> In-Reply-To: <55B7EB30.9020008@gmail.com> Date: Fri, 31 Jul 2015 22:55:14 +0200 Message-ID: <029b01d0cbd3$35538b70$9ffaa250$@belski.net> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable X-Mailer: Microsoft Outlook 15.0 Thread-Index: AQGkqh/2VO9aX+2MxEE5sWEw0iYXWwJIWw7YAnhH4mICg0zaigHVuucuAbM2VxQCDsLRDgFi10ZGndxbNTA= Content-Language: en-us Subject: RE: [PHP-DEV] Re: Serializing exceptions From: anatol.php@belski.net ("Anatol Belski") Hi Stas, > -----Original Message----- > From: Stanislav Malyshev [mailto:smalyshev@gmail.com] > Sent: Tuesday, July 28, 2015 10:51 PM > To: Marco Pivetta ; Rowan Collins > > Cc: Nikita Popov ; PHP Internals List > > Subject: Re: [PHP-DEV] Re: Serializing exceptions >=20 > Hi! >=20 > > New BC breaks in Beta? >=20 > Why not? What's the problem with it? Beta is to identify issues with = current > code, serialized exceptions is an issue (as in, they don't work and = lead to security > problems and generally pointless). Dragging this known problem around = for > years makes no sense. I was looking through and seems that situation is not that bad. Reading = http://fabien.potencier.org/php-serialization-stack-traces-and-exceptions= .html it might be not that meaningful to break symphony. Having upset = users is logic as long as we don't offer a solution, while the = functionality itself seems to make sense. And after all serialization = looks useful in some cases (logging at least). Maybe we should go more = fine tuning way, maybe ignoring the thing that cannot be serialized. = Say, serializing only a white list in this case? Regards Anatol