Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:65854
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.215.52 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <713003612.20130214164753@cypressintegrated.com>
References: <511CEEB1.7040303@hoa-project.net>
	<511D5924.4070602@sugarcrm.com>
	<713003612.20130214164753@cypressintegrated.com>
Date: Fri, 15 Feb 2013 07:41:22 +0100
Message-ID: <CAEZPtU5pr8K5yJY+owKMDMX49aVY3N_eHuXaeqO4fiOiJCdzgg@mail.gmail.com>
To: Sanford Whiteman <swhitemanlistens-software@cypressintegrated.com>
Cc: Stas Malyshev <internals@lists.php.net>
Content-Type: text/plain; charset=ISO-8859-1
Subject: Re: [PHP-DEV] File system watcher/monitoring
From: pierre.php@gmail.com (Pierre Joye)

hi,

On Thu, Feb 14, 2013 at 10:47 PM, Sanford Whiteman
<swhitemanlistens-software@cypressintegrated.com> wrote:
>> I think it'd be great to have a library with unified interface and an
>> extension that uses it. However, I'm not sure if these libraries are
>> useful in common php use case - short-lived requests. Could I get the
>> changes since the last request? Or is it useful only for long-running
>> persistent processes?
>
> You're right of course that you are implicitly lengthening a request.
> But if you are already embracing a long-polling model that waits for
> filesystem changes, the back-end service can actually use fs events
> instead of looping -- much more efficient. In fact I do this already
> on Windows by running an external FileSystemWatcher EXE and waiting
> for it to return (+ a timeout in the wrapper).


There are native APIs for that (read: non .net, aka C) on Windows,
using an external process for this purpose would be horrible, in all
possible ways.

Cheers,
-- 
Pierre

@pierrejoye