DBus for Generic Data Access Methods?
marcel at holtmann.org
Tue Jan 30 13:27:06 CET 2007
> > You have to understand that the object path is not the unique element in
> > the D-Bus architecture.
> Yep I understand this bit and that's why I think abstracting the paths
> works. Say you have three separate items that provide address
> information on the paths:
> And you have written a GPS application that would like to obtain the
> home location of a known user and plot that location on a map. It has
> to ask the three separate applications if they have the address of the
> user, and to do that it needs each application's object path.
> Now say a new developer looks at OpenMoko and says "Cool; I'll link
> this with my social networking site." So off they go and writes an
> application that can look up a user on their social networking site, and
> sets up an object path of /com/socialsite/lookupperson. The problem is
> that none of the existing applications will talk to it as they don't
> know about it, so it just doesn't work. My point is that if there is a
> well-known object path, say /org/OpenMoko/contacts, then everyone could
> use the same object path and as new applications are added that it gets
> added to the list and everything just works.
the question is still why. We have EDS. So no reason to invent another
interface for the same purpose. Don't try to over-complicate things.
More information about the openmoko-devel