[RFC] dbus-python API (re)definition

[Daniel P. Berrange]

On Thu, Aug 31, 2006 at 04:50:55PM +0100, Simon McVittie wrote:
> There should probably be some sort of API for watches so you can run
> dbus-python without using the glib mainloop (perhaps in Twisted, Tkinter or
> PyQT code). I'm not sure at this point whether Messages and PendingCalls
> should be exposed to Python code or not - what functionality would we
> lose if they aren't?

I agree the low level Message & PendingCall objects should not be exposed
directly - the only reason they need to be curently is because the bindings
are incomplete in places. In the Perl bindings I created a higher level
abstraction around PendingCalls, which I called  AsyncReply.  It justs 
provides a good way to get notified when an async method call complete & 
to get the list of return parameters without having to deal with Message 
objects directly like you would if using PendingCall directly.  With such
an abstraction there should be no need for app developers to use PendingCall
or Message objects.

> Comments?

All sounds like a very good plan.

Dan.
-- 
|=-            GPG key: http://www.berrange.com/~dan/gpgkey.txt       -=|
|=-       Perl modules: http://search.cpan.org/~danberr/              -=|
|=-           Projects: http://freshmeat.net/~danielpb/               -=|
|=-   berrange at redhat.com  -  Daniel Berrange  -  dan at berrange.com    -=|
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url : http://lists.freedesktop.org/archives/dbus/attachments/20060831/ff85331a/attachment.pgp