Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:48729 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 62578 invoked from network); 10 Jun 2010 16:00:14 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 10 Jun 2010 16:00:14 -0000 Authentication-Results: pb1.pair.com smtp.mail=rasmus@lerdorf.com; spf=permerror; sender-id=unknown Authentication-Results: pb1.pair.com header.from=rasmus@lerdorf.com; sender-id=unknown Received-SPF: error (pb1.pair.com: domain lerdorf.com from 209.85.160.42 cause and error) X-PHP-List-Original-Sender: rasmus@lerdorf.com X-Host-Fingerprint: 209.85.160.42 mail-pw0-f42.google.com Received: from [209.85.160.42] ([209.85.160.42:46986] helo=mail-pw0-f42.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id EB/68-17116-D0C011C4 for ; Thu, 10 Jun 2010 12:00:14 -0400 Received: by pwi4 with SMTP id 4so47827pwi.29 for ; Thu, 10 Jun 2010 09:00:11 -0700 (PDT) Received: by 10.141.214.40 with SMTP id r40mr289811rvq.11.1276185610950; Thu, 10 Jun 2010 09:00:10 -0700 (PDT) Received: from Rasmus-Lerdorfs-MacBook-Pro.local (c-24-7-29-193.hsd1.ca.comcast.net [24.7.29.193]) by mx.google.com with ESMTPS id b2sm146761rvn.7.2010.06.10.09.00.09 (version=TLSv1/SSLv3 cipher=RC4-MD5); Thu, 10 Jun 2010 09:00:09 -0700 (PDT) Message-ID: <4C110C07.9000201@lerdorf.com> Date: Thu, 10 Jun 2010 09:00:07 -0700 User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.1.9) Gecko/20100317 Thunderbird/3.0.4 MIME-Version: 1.0 To: Tjerk Anne Meesters CC: Brian Moon , internals References: <4C10FD00.1050204@lerdorf.com> <4C1102D4.6080105@moonspot.net> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] Gearman support for php-fpm? From: rasmus@lerdorf.com (Rasmus Lerdorf) On 6/10/10 8:53 AM, Tjerk Anne Meesters wrote: > All "fpm" workers would be called using the same function name (e.g. > "runphp"). This allows you to reuse a gearmand instance for other > workers too. I don't think we would need to require that. Obviously you could build your Gearman worker such that it registers "runphp" and has a big switch in it to run various types of jobs and fpm would just need to manage a single pool of workers. But, assuming fpm could manage multiple pools, I don't see the problem with having different types of workers. -Rasmus