On Fri, Sep 19, 2008 at 01:14:14PM +0200, Gerd Hoffmann wrote: > Daniel P. Berrange wrote: > > Applications could either craft their event loop impl themselves, or > > we can provide some add-on pre-built helper libraries with common > > impls. eg, an optional libvirt-glib library which comes with a > > pre-built event impl for applications which use glib. Likewise a > > libvirt-qt helper. That'd cover pretty much all common GUI apps. > > Sounds sane. avahi does the same btw, and I like that approach. Avahi's interface is a thin wrapper arounds dbus's interface :-) And indeed the libvirtd's event.c impl fits into Avahi's interface nicely which demonstrates we're consistent in our thinking. Daniel -- |: Red Hat, Engineering, London -o- http://people.redhat.com/berrange/ :| |: http://libvirt.org -o- http://virt-manager.org -o- http://ovirt.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: GnuPG: 7D3B9505 -o- F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :| -- Libvir-list mailing list Libvir-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/libvir-list