Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:65855 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 81856 invoked from network); 15 Feb 2013 07:35:19 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 15 Feb 2013 07:35:19 -0000 Authentication-Results: pb1.pair.com smtp.mail=swhitemanlistens-software@cypressintegrated.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=swhitemanlistens-software@cypressintegrated.com; sender-id=pass Received-SPF: pass (pb1.pair.com: domain cypressintegrated.com designates 173.1.104.101 as permitted sender) X-PHP-List-Original-Sender: swhitemanlistens-software@cypressintegrated.com X-Host-Fingerprint: 173.1.104.101 rproxy2-b-iv.figureone.com Windows 2000 SP2+, XP SP1 (seldom 98 4.10.2222) Received: from [173.1.104.101] ([173.1.104.101:56821] helo=rproxy2-b-iv.figureone.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 4F/60-13024-535ED115 for ; Fri, 15 Feb 2013 02:35:18 -0500 Received: from localhost ([216.220.114.66]) by rproxy2-b-iv.figureone.com (Brand New Heavy v1.0) with ASMTP id AJY41814 for ; Thu, 14 Feb 2013 23:35:14 -0800 Date: Fri, 15 Feb 2013 02:35:06 -0500 Reply-To: Sanford Whiteman X-Priority: 3 (Normal) Message-ID: <1331291088.20130215023506@cypressintegrated.com> To: Pierre Joye CC: Stas Malyshev In-Reply-To: References: <511CEEB1.7040303@hoa-project.net> <511D5924.4070602@sugarcrm.com> <713003612.20130214164753@cypressintegrated.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] File system watcher/monitoring From: swhitemanlistens-software@cypressintegrated.com (Sanford Whiteman) > There are native APIs for that (read: non .net, aka C) on Windows Well aware of that. The EXE does use the Win32 API, not a .NET wrapper. I've used that API ever since it's been documented. > using an external process for this purpose would be horrible, in all > possible ways. Well, yeah, that's my very point... having the engine/extension do this is the proper direction (I only use this hack to check completion of some scheduled tasks, it's all private). Stas says typical PHP apps don't have a need for file system hooks. Sure, long-polling may not be good with thread-per-process webservers, but those aren't the only PHP environments in the wild. Once you accept that people already roll out long-polling back ends with PHP, the next step is to minimize the check-sleep-loop hackery and offer true event-driven alternatives when possible. Nothing I'm saying is controversial. -- Sandy