DNOTIFY support and some timing

Tim Jansen tim at tjansen.de
Wed Mar 5 00:03:31 GMT 2003

On Wednesday 05 March 2003 00:21, Christian Esken wrote:
> > This interval determines how much time it takes on average before an
> > application that gets installed appears in the KDE menu. There are also
> > other contributing factors, such as the time kbuildsycoca takes to run.
> Finished ? :)
> I'll post some test results while you're busy hacking.

BTW I wonder whether it wouldn't be better to grab some kernel guy (<g>) and 
talk about implementing events that would be useful for desktop systems. That 
would include:

- the ability to watch directories (optionally including subdirectories) with 
sane filters that reduce traffic. This is not only important for Konqueror, 
but also for all applications that index files or collect meta-information 
about them (http://dot.kde.org/1042011702/)
- notifications when a file system is being mounted/unmounted
- notifications when a CD-ROM has been inserted/ejected (without having to 
block the /dev file for other apps)
- notifications for network events (new network interface comes up, goes down, 
cable plugged in, plugged out)
- device notifications / hotplug stuff which is now handled by the hotplug 

Recently Linux 2.5 got the ability to deliver signals using poll()/select(), 
see http://lwn.net/Articles/22699/. This means that the kernel now gets the 
infrastructure to create file descriptors for events that are not related to 
a socket or a stream, and it may be very useful for a couple of other things. 
Using signals for events obviously sucks in GUI apps that use a event loop.


More information about the kde-core-devel mailing list