KDE adoption of D-Bus

[Thiago Macieira]

John (J5) Palmieri wrote:
>> 1) Windows and MacOS X support
>> KDE4 (or at least KDE 4 applications) is supposed to run on both of
>> those platforms. Has libdbus been ported to those platforms? Does it
>> work? Are there known problems?
>
>There was someone doing a port to OS X.  He ran into problems
>propagating the session service address and also running as part of a
>bundle.  How does DCOP get around this?

I don't know. I'll investigate.

>> 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 it can't connect, then it starts dcopserver and waits for the server to 
be available.

>> I can provide the code myself in the Qt bindings or whichever KDE
>> wrapper we write, but I would rather see a common solution. Especially
>> considering this will very likely be the case for Windows and MacOS X.
>
>It would be good to solve this issue in D-Bus itself, I agree.

-- 
  Thiago Macieira  -  thiago (AT) macieira.info - thiago (AT) kde.org
    PGP/GPG: 0x6EF45358; fingerprint:
    E067 918B B660 DBD1 105C  966C 33F5 F005 6EF4 5358

5. Swa he géanhwearf tó timbran, and hwonne he cóm, lá! Unix cwæð "Hello, 
World". Ǽfre ǽghwilc wæs glæd and seo woruld wæs fréo.
-------------- 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/ff8160c2/attachment.pgp