Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:54707 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 13096 invoked from network); 19 Aug 2011 08:57:01 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 19 Aug 2011 08:57:01 -0000 Authentication-Results: pb1.pair.com header.from=sebastian.krebs.berlin@googlemail.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=krebs.seb@googlemail.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain googlemail.com designates 209.85.214.42 as permitted sender) X-PHP-List-Original-Sender: krebs.seb@googlemail.com X-Host-Fingerprint: 209.85.214.42 mail-bw0-f42.google.com Received: from [209.85.214.42] ([209.85.214.42:37830] helo=mail-bw0-f42.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 8E/20-11562-6552E4E4 for ; Fri, 19 Aug 2011 04:56:55 -0400 Received: by bkd19 with SMTP id 19so2206827bkd.29 for ; Fri, 19 Aug 2011 01:56:51 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=mime-version:sender:x-google-sender-delegation:in-reply-to :references:date:x-google-sender-auth:message-id:subject:from:to :content-type; bh=KiQvNi649ARFn5GXdHM39+/Fo51cIWvUrbPU4lp4xRw=; b=WoaHBYz1AEdJkqOu3khQjLQVMrFtzSurYwBNNijfDVCeb6iLzCyPsR+20zeFVAE90z Aq8rfwrludLYfN17/4mSSOnchNVSyOVmn4IPU1siOmG8kAzB/cVzA75k7lYRvzUStey+ ha75HoyxjUfznn+Rfm0Bd5ZLLjpj+sgRPcyug= MIME-Version: 1.0 Received: by 10.204.132.68 with SMTP id a4mr228784bkt.154.1313744210906; Fri, 19 Aug 2011 01:56:50 -0700 (PDT) Sender: sebastian.krebs.berlin@googlemail.com X-Google-Sender-Delegation: sebastian.krebs.berlin@googlemail.com Received: by 10.204.36.13 with HTTP; Fri, 19 Aug 2011 01:56:50 -0700 (PDT) In-Reply-To: <4E4E1561.8070305@kingsquare.nl> References: <4E4D4B8D.6090406@sugarcrm.com> <4E4E1561.8070305@kingsquare.nl> Date: Fri, 19 Aug 2011 10:56:50 +0200 X-Google-Sender-Auth: -RdnMBQkuGLhnbV0EhtZvf2TFlE Message-ID: To: internals@lists.php.net Content-Type: multipart/alternative; boundary=000e0cd6cfcc044e7b04aad7e930 Subject: Re: [PHP-DEV] Activation of IGBinary serialization extension in 5.4 by default From: krebs.seb@googlemail.com (Sebastian Krebs) --000e0cd6cfcc044e7b04aad7e930 Content-Type: text/plain; charset=ISO-8859-1 Hi, One pitfall I see is, that two separate system can communicate using serialized data. They both must understand the same format and (in this case) must be configured equal. Regards, Sebastian 2011/8/19 Kingsquare.nl - Robin Speekenbrink > Dear All, > > Again with my 2cents into the basket: I was hoping Ilia Alshanetsky would > also support this idea since in his talks (i.e. > http://ilia.ws/archives/241-**IPC-Hidden-Features-of-PHP-**Slides.html) > he has been promoting the exact same use: switch the standard serializer to > igBinary... > > Also the proposed include it -> read the data -> convert on write if in > previous format (possibly an ini setting?) would provide full BC and would > allow a painless upgrade... wouldnt it? > > -- > With kind regards, > > Robin Speekenbrink > Kingsquare Information Services > > On donderdag 18 augustus 2011 21:39:56, Pierre Joye wrote: > >> hi Stas! >> >> On Thu, Aug 18, 2011 at 7:27 PM, Stas Malyshev> >> wrote: >> >> . not enabling it by default defeats the purpose of bundling it >>>> >>> >>> Actually, I don't think it does. It's one thing to tell people "put this >>> option into php.ini" and quite another is "download it from PECL (?), >>> compile it (?!) and install it". The first is wi >>> >> thin the limits of any > >> literate person, the second is sysadmin territory. >>> >> >> All major distros have it already, so it is the same. Now, if it is >> not enabled by default, then many admins won't install it, back to the >> same problem. It is very unlikely that someone with root or admin >> perms won't be able to install an extra extension from the distro >> repository or using the DLL on windows. >> >> . easier to support it while being only in pecl ('do you use the core >>>> version or latest pecl?") >>>> >>> >>> It is a concern, if this extension is not stable yet. Is it? >>> >> >> It is stable. But the concern is not about its stability but the ease >> of support. Having it in core means than some users may use (for >> example) 5.4.2 version while we are at 5.4.6 or pecl has 3 new >> versions. Not a big deal, just easier. >> >> That being said, I'm not opposed to include it, I only don't see it as >> a must go :) >> >> Cheers, >> > > -- > PHP Internals - PHP Runtime Development Mailing List > To unsubscribe, visit: http://www.php.net/unsub.php > > --000e0cd6cfcc044e7b04aad7e930--