(DBUS/Python) async_callbacks vs. reply_/error_handler

[Pavel Strashkin]

Hi Jason,

There is the only one difference. You use reply_handler/error_handler
to implement async work on a client side and you use async_callbacks
to implement async work on a service side. You can't use
dbus.service.method (and async_callbacks) for the clients.

2011/2/17 Jason Heeris <jason.heeris at gmail.com>:
> I'm using the Python/DBUS bindings for asynchronous inter-process
> calls in my Twisted/PyGTK app.
>
> I know about using the "reply_handler"/"error_handler" for calling
> methods on proxy objects, and connecting to signals, but I've also
> read about the "async_callbacks" argument to the dbus.service.method
> decorator[1].
>
> The problem is, the section of the docs that should detail this[2] is empty...
>
> So what's the difference? If I have an "async_callbacks" argument in
> my service, will a call on the proxy object in another process behave
> any differently than if I used the "reply_handler"/"error_handler"
> arguments? How can I decide which is best for my situation?
>
> Cheers,
> Jason
>
> [1] http://stackoverflow.com/questions/2142115/implementation-of-an-async-method-in-python-dbus
> [2] http://dbus.freedesktop.org/doc/dbus-python/doc/tutorial.html#asynchronous-method-implementations
> _______________________________________________
> dbus mailing list
> dbus at lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/dbus
>