Why should anyone use the synchronous API?
John (J5) Palmieri
johnp at redhat.com
Wed Mar 1 06:51:14 PST 2006
Synchronous APIs are a lot easier to deal with and in the case of
non-gui apps it is often the way to go. Some apps can also use threads
in conjunction with the blocking API to get async behavior. The
tutorial is to get people up and running fast and understanding the
basics of D-Bus and IPC. The tutorial should start with the sync API's
because it is what most programmers are use to. It should also cover
the async API, building on the sync API. It should not be tutorial on
why async is better than sync because that is up to the application
developer based on their requirements.
On Wed, 2006-03-01 at 11:50 +0100, DANIELLLANO at terra.es wrote:
> David Zeuthen wrote:
> > The glib bindings currently just sets the timeout of method calls to -1.
> > This is pretty bad so I've written a patch that fixes it. Unfortunately
> > it breaks some API but we'd better fix this. For details see
> > http://bugzilla.gnome.org/show_bug.cgi?id=332888
> Why do dbus needs this kind of problems?
> I mean, Why dbus needs a synchronous API?
> What's the use case of the synchronous API?
> I think the asynchronous API should be the default one and only use the
> synchronous API by legacy applications that don't work well with the glib
> main loop.
> Shouldn't everyone be encouraged to only use the synchronous API (at
> least in new applications)?
> I think that the tutorial
> should only explain asynchronous calls.
> Prueba el Nuevo Correo Terra; Seguro, Rápido, Fiable.
> dbus mailing list
> dbus at lists.freedesktop.org
More information about the dbus