RFC: Annotations for object path data type
hp at redhat.com
Sat Jan 14 10:17:49 PST 2006
There are some old posts in the archives I think about "object
references" (what corba calls an IOR) which would roughly be bus address
+ bus name + object path iirc. With that concept you could create
"location transparent" object references.
It seems like you have to confront the "memory management" issue - my
only advice is that the object provider code really needs to recover if
the client goes away without calling delete/unref...
On relative vs. absolute paths: would it be simpler to just declare that
the object paths are always absolute? I think that was my assumption...
I hadn't considered that people would do relative ones.
More information about the dbus