[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-core-devel
Subject:    Re: DNOTIFY support and some timing
From:       Alexander Neundorf <neundorf () kde ! org>
Date:       2003-03-05 16:23:43
[Download RAW message or body]

On Wednesday 05 March 2003 01:03, Tim Jansen wrote:
> 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
> script
>
>
> 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.

A small addition, currently this "event" interface is used to receive selected 
signals (yes, the UNIX signals) synchronously via poll()/select(), but this 
way they become a really nice thing, I think.
But unfortunately this is probably unportable for now.

Bye
Alex
-- 
Work: alexander.neundorf@jenoptik.com - http://www.jenoptik-los.de
Home: neundorf@kde.org                - http://www.kde.org
      alex@neundorf.net               - http://www.neundorf.net

[prev in list] [next in list] [prev in thread] [next in thread]