Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:65869 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 15856 invoked from network); 15 Feb 2013 12:57:01 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 15 Feb 2013 12:57:01 -0000 Authentication-Results: pb1.pair.com smtp.mail=ivan.enderlin@hoa-project.net; spf=permerror; sender-id=unknown Authentication-Results: pb1.pair.com header.from=ivan.enderlin@hoa-project.net; sender-id=unknown Received-SPF: error (pb1.pair.com: domain hoa-project.net from 95.130.12.24 cause and error) X-PHP-List-Original-Sender: ivan.enderlin@hoa-project.net X-Host-Fingerprint: 95.130.12.24 host1.trois-doubles.net Linux 2.6 Received: from [95.130.12.24] ([95.130.12.24:55593] helo=host1.trois-doubles.net) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 87/91-06160-B903E115 for ; Fri, 15 Feb 2013 07:57:00 -0500 Received: from Hwhost2.local (158-63.203-62.cust.bluewin.ch [62.203.63.158]) by host1.trois-doubles.net (Postfix) with ESMTPSA id B872420A9D2 for ; Fri, 15 Feb 2013 13:56:56 +0100 (CET) Message-ID: <511E3097.1020607@hoa-project.net> Date: Fri, 15 Feb 2013 13:56:55 +0100 Reply-To: ivan.enderlin@hoa-project.net User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:20.0) Gecko/20100101 Thunderbird/20.0a2 MIME-Version: 1.0 To: internals@lists.php.net References: <511CEEB1.7040303@hoa-project.net> <511CF6D2.5050108@hoa-project.net> <511CF9A9.4030205@hoa-project.net> In-Reply-To: Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: quoted-printable Subject: Re: [PHP-DEV] File system watcher/monitoring From: ivan.enderlin@hoa-project.net ("Ivan Enderlin @ Hoa") On 14/02/13 18:02, Paul Dragoonis wrote: > On Thu, Feb 14, 2013 at 5:00 PM, Patrick ALLAERT wrote: > >> 2013/2/14 Ivan Enderlin @ Hoa : >>> I have written: =93On Linux, we have inotify (available in PHP throug= h >>> pecl/inotify)=94, so yup, I know for inotify :-). I propose to gather= all >>> these API and give a proper one to the end-user. >> If you are doing so, I would suggest you to create this as a C >> library, that way you could bring that feature to any >> applications/languages and you would only have to create a bridge as a= >> PECL extension. >> > and to carry on from Patrick's point, it would probably be cleaner to d= o it > this way so your library wouldn't need to work around PHP stuff. Actually, I have already considered this approach, but to make a clean=20 and portable C version, it might be better to use external existing=20 libraries (e.g. for events). This might create hard dependencies and=20 could be embarassing for a PECL extension, no? Thoughts? --=20 Ivan Enderlin Developer of Hoa http://hoa-project.net/ PhD. student at DISC/Femto-ST (Vesontio) and INRIA (Cassis) http://disc.univ-fcomte.fr/ and http://www.inria.fr/ Member of HTML and WebApps Working Group of W3C http://w3.org/