Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
Message from discussion FPM in 5.3

Received: by 10.141.22.14 with SMTP id z14mr3425173rvi.28.1274948185820;
        Thu, 27 May 2010 01:16:25 -0700 (PDT)
X-BeenThere: highload-php-en@googlegroups.com
Received: by 10.140.255.17 with SMTP id c17ls829159rvi.2.p; Thu, 27 May 2010 
	01:16:23 -0700 (PDT)
Received: by 10.141.124.12 with SMTP id b12mr3416592rvn.27.1274948183862;
        Thu, 27 May 2010 01:16:23 -0700 (PDT)
Received: by 10.141.124.12 with SMTP id b12mr3416591rvn.27.1274948183840;
        Thu, 27 May 2010 01:16:23 -0700 (PDT)
Return-Path: <alexey.ry...@gmail.com>
Received: from mail-px0-f176.google.com (mail-px0-f176.google.com [209.85.212.176])
        by gmr-mx.google.com with ESMTP id 24si152438pzk.1.2010.05.27.01.16.22;
        Thu, 27 May 2010 01:16:22 -0700 (PDT)
Received-SPF: pass (google.com: domain of alexey.ry...@gmail.com designates 209.85.212.176 as permitted sender) client-ip=209.85.212.176;
Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of alexey.ry...@gmail.com designates 209.85.212.176 as permitted sender) smtp.mail=alexey.ry...@gmail.com; dkim=pass (test mode) header...@gmail.com
Received: by pxi10 with SMTP id 10so3210027pxi.21
        for <highload-php-en@googlegroups.com>; Thu, 27 May 2010 01:16:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=gamma;
        h=domainkey-signature:mime-version:received:received:in-reply-to
         :references:date:message-id:subject:from:to:content-type;
        bh=IN9EFRwS3O7KkS6qy/wZsxUzg+VJDQpWzAY1axyDpYg=;
        b=ONW/zvXiP5qXDGpGP3qFiFf2ErB287nwtd6V6g+/CeP8aFtVkDpULxcufwxLERHBVy
         9bw1KfiAl9BW1vZPWvnoiZSeYrH9AyeuOcZMlIiXDEbeW7efOi/S5E947PkJr4XdIETI
         aGmXxIrDwAZYXckMdGv6F6onZdzwnf3O76FHM=
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type;
        b=WNYMccEQI+j0odVJFc1reIr3S+yW5VaC9BdXVw7qleGthHWbU1LcxiNm+AG9Dd6KL4
         B4WK4ipOmq+IwaENcKu47of6WZ3i2FHPl8uaGFk/BUckqpDtTtvxHzvfNXgXsHvuCyFU
         /Pk0jRozIn38gR9n+4B0RFP4wBuzNc06zjkCE=
MIME-Version: 1.0
Received: by 10.141.14.12 with SMTP id r12mr7620006rvi.94.1274948182633; Thu, 
	27 May 2010 01:16:22 -0700 (PDT)
Received: by 10.140.141.7 with HTTP; Thu, 27 May 2010 01:16:22 -0700 (PDT)
In-Reply-To: <4BFD3E5E.1050...@daylessday.org>
References: <4BFD3E5E.1050...@daylessday.org>
Date: Thu, 27 May 2010 12:16:22 +0400
Message-ID: <AANLkTimSeSNODtazEn4xe2Bkp2L7NBkfxFsz_5ua0...@mail.gmail.com>
Subject: Re: FPM in 5.3
From: "Alexey A. Rybak" <alexey.ry...@gmail.com>
To: highload-php-en@googlegroups.com
Content-Type: text/plain; charset=ISO-8859-1

ura! thank you all guys

On Wed, May 26, 2010 at 7:29 PM, Antony Dovgal <t...@daylessday.org> wrote:
> Hello all.
>
> After a short discussion with Rasmus and Johannes (how's maintaining PHP 5.3 branch) it was agreed that FPM
> can't break anything serious and even though 5.3 is a bugfix branch, it's safe to add FPM there.
>
> Which was done several minutes ago.
>
> So now you don't have to checkout PHP trunk, copy sapi/fpm to your 5.3 source tree and so on - it's all there already.
> Snapshots containing FPM will be ready in ~1 hour, according to http://snaps.php.net.
> Feel free to test them and report any issues you find using the official bug tracker @ http://bugs.php.net.
>
> P.S. no way to add it to 5.2, sorry.


-- 

wbr,
fisher