KDE adoption of D-Bus

[Waldo Bastian]

On Wednesday 15 February 2006 08:06, Thiago Macieira wrote:
> >> In other words, is it possible to use D-Bus session if the daemon
> >> isn't running and DBUS_SESSION_BUS_ADDRESS isn't set?
> >
> >There is no solution for doing this right now.  How do application find
> >out what DCOP instance to talk to?
>
> There is only one DCOP instance per X display. And it saves its socket
> address to a file called
>   $HOME/.DCOPserver_${HOSTNAME}_${DISPLAY}
>
> $ cat $HOME/.DCOPserver_${HOSTNAME}_${DISPLAY}
> local/marslander:/tmp/.ICE-unix/dcop4821-1139404385
> 4821

If this is being copied, please note that any ':' in $HOSTNAME or $DISPLAY is 
replaced with '_', some file systems don't support ':' in names.  

> If it can't connect, then it starts dcopserver and waits for the server to
> be available.

Note that this means that remote clients get (and share) their own DCOP 
session at the remote server. I think that's a reasonable approach for most 
situations.

Cheers,
Waldo
-- 
Linux Client Architect - Channel Platform Solutions Group - Intel Corporation
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://lists.freedesktop.org/archives/dbus/attachments/20060215/cf83b2c5/attachment.pgp