Re: File system watcher/monitoring
| From: | Ivan Enderlin @ Hoa | Date: | Fri, 15 Feb 2013 12:56:55 +0000 |
| Subject: | Re: File system watcher/monitoring | ||
| References: | 1 2 3 4 5 6 7 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-65869@lists.php.net to get a copy of this message | ||
On 14/02/13 18:02, Paul Dragoonis wrote:
On Thu, Feb 14, 2013 at 5:00 PM, Patrick ALLAERT <patrickallaert@php.net>wrote:Thoughts? -- 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/2013/2/14 Ivan Enderlin @ Hoa <ivan.enderlin@hoa-project.net>:and to carry on from Patrick's point, it would probably be cleaner to do 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 and portable C version, it might be better to use external existing libraries (e.g. for events). This might create hard dependencies and could be embarassing for a PECL extension, no?I have written: “On Linux, we have inotify (available in PHP through pecl/inotify)”, 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.