From dfb0c1845a8937dbb1e669c16a2ed36547a8a00f Mon Sep 17 00:00:00 2001 From: Ulf Lilleengen Date: Sat, 18 Jul 2009 12:21:39 +0200 Subject: - Remove pnotify library again as the API is a bit messy and handles things in a different way than musicfs requires. --- pnotify/pnotify-0.2/index.html | 117 ----------------------------------------- 1 file changed, 117 deletions(-) delete mode 100644 pnotify/pnotify-0.2/index.html (limited to 'pnotify/pnotify-0.2/index.html') diff --git a/pnotify/pnotify-0.2/index.html b/pnotify/pnotify-0.2/index.html deleted file mode 100644 index 0da304d..0000000 --- a/pnotify/pnotify-0.2/index.html +++ /dev/null @@ -1,117 +0,0 @@ - - -pnotify - a portable filesystem event notifier - - -

pnotify

-pnotify is an event notification framework for monitoring files and directories. -It is designed to be portable across different Unix-like operating systems, and currently -supports Linux and BSD. The pnotify API is very similar to the inotify API under Linux. - -
-
-Download | -Documentation | -Mailing list -
- -
- -

Rationale

- -Kernel-based filesystem event notification is a relatively new phenonemon, and several -different approaches have been taken by various operating systems. -Linux uses inotify, BSD uses kqueue, Apple has kqueue and it's own Spotlight system calls, Solaris has FEM, Windows has the NTFS Change Journal and the ReadDirectoryChangesW function, and so forth. -

-The goal of pnotify is to provide a simple, cross-platform API for monitoring filesystem -events. The library will conceal all of the messy implementation-specific details from the user and help them to write more portable programs. - -

History

- -pnotify was born out of an effort to port the inotify API from Linux -to BSD. This initial effort took the form of a userspace library that would translate -inotify requests into their kqueue(4) equivalent. After some time, it became clear that -kqueue was not sophisticated enough to support all of the functionality of inotify. -There was also the problem of threadsafety; inotify relies on shared global data -structures, which is normal within the kernel but complicates the design of a userspace library. -

-Eventually, it became clear that a new API was needed to address these portability and threadsafety issues. This new API became 'pnotify', to indicate that it is a portable subset of the -inotify API. - -

Supported Platforms

- -pnotify has been ported to the following platforms: - - - -There are platforms that are not supported due to lack of developer resources. -Interested parties with access to these platforms are encouraged to port -the library to their platform. For example: - -

-

-

-At the current time, there is no generic polling mechanism to use as a fallback -for systems that don't have a kernel event mechanism like inotify or kqueue. - -

Usage

- -When you run './configure && make && make install', pnotify is built -as a shared library and installed under the /usr/local prefix. -

-Even though pnotify is built as a shared library by default, -it is easier for application developers to include -pnotify.c and pnotify.h in their source tree and not depend -on the existence of a shared library. - - -

Download

- - -The source code may be downloaded from the download page. You may also check out a working copy of the latest -development sources by issuing the following command: -

- -svn checkout http://pnotify.googlecode.com/svn/trunk/ pnotify - -

-If you just want a quick peek at the source code, you can browse the webSVN repository - - -

Documentation

- - - - -

Mailing List

- -There is a mailing list for discussion about the pnotify library. Click -here to sign up, -post a question or comment, or browse through the archives. - -

Contact the Author

- -For more information, contact Mark Heily at devel@heily.com - -

Related Links

- - -
-(C) 2007 Mark Heily. - - -- cgit v1.2.3