[Telepathy] D-Bus tube establishment, and races
muadda at gmail.com
Fri Jan 25 08:48:13 PST 2008
On Jan 25, 2008 9:31 AM, Guillaume Desmottes
<guillaume.desmottes at collabora.co.uk> wrote:
> I'm not sure about your race issue. Is that wrong if we connect to a
> private D-Bus bus while the initiator isn't connected to it? I'm
> wondering if it's not the responsibility of the application using the
> tube to be sure there are actually participants in it.
> IIRC we send our D-Bus name when we offer or accept the tube (and so
> DbusNameChanged is fired on remote clients). Maybe we should send it
> only when we have actually joined the tube?
Applications need a reliable way to know that the other end of the
tube is connected to the D-Bus address. I don't know if firing
DbusNameChanged after the other end has connected to the D-Bus address
is the right thing to do.
With dbus-daemon, a client can call a method even when the server is
not yet started thanks to the D-Bus activation feature. Maybe the CM
on the server side can have a similar "activation" feature: the CM can
wait the server application to connect to the D-Bus address, and then
the CM deliver the method call message to the server application.
More information about the Telepathy