On Sun, 21.02.10 14:50, Bastien Nocera ([email protected]) wrote: > - The plugin API should instead be a convenience library around using > the D-Bus API, which would make implementing other front-ends to those > plugins easier.
With D-Bus API you mean http://live.gnome.org/Rygel/MediaServerSpec? I thought the general approach to D-Bus these days was not to provide any wrapper libraries but have clients use the D-Bus APIs directly, with the native interfacing of their programming language/environment, be that eggdbus, python-dbus or Vala's native D-Bus support. > I guess it wouldn't be powerful enough for some plugins > though, Can you elaborate on that? Which ones do you mean? > so maybe it should be an interface with 2 possible > implementations, and the more powerful one having some extra > functionality. Hmm, I am not sure I follow? Lennart -- Lennart Poettering Red Hat, Inc. lennart [at] poettering [dot] net http://0pointer.net/lennart/ GnuPG 0x1A015CC4 _______________________________________________ desktop-devel-list mailing list [email protected] http://mail.gnome.org/mailman/listinfo/desktop-devel-list
