View Single Post
Posts: 1,048 | Thanked: 979 times | Joined on Mar 2008 @ SF Bay Area
#64
Originally Posted by epage View Post
I mean keeping your interfaces backwards compatible. A user could update this application while not updating a couple others. If you changed your DBus interfaces then the apps will break.

That plus the fact that an dbus api already exists (telepathy) is why I pushed back on the idea of a dbus api
I agree about the backwards compatibility and also know that telepathy would be the ideal interface.
I guess providing any external interface would entail making sure that interface does not change in any future releases.
Versioning that interface is what I think I will need to do and that would need a handshake and more...

This might turn out to be much more than I had intended.
__________________
qgvdial: Google Voice client. All downloads
qgvtp: Phone integration for the n900 that dials out and sends texts using qgvdial.
mosquitto: message broker that implements the MQ Telemetry Transport protocol version 3.
qgvnotify: Google voice and contacts notifier for diablo and maemo.

If you want to thank me, click the Thanks button.
If you'd like to thank my applications, vote to move them to extras.