Issue with _dbus_write_socket on windows

Havoc Pennington hp at
Sun Nov 19 10:12:57 PST 2006

Christian Ehrlicher wrote:
> Havoc Pennington schrieb:
>> Christian Ehrlicher wrote:
>>> Thx, for the hints. Now the daemon is started on demand and adress is
>>> read from shared memory.
>> How did you go about making it per-user instead of per-machine?
> Currently this is not supported, but I think it should be possible by
> adding a userid or something else to the shm name.

My .02, I don't think this is a "would be nice" feature - it's pretty 
essential to dbus working right.

> But the bigger
> problem is - how can I avoid using the same port twice? And how can I
> react when the port is already in use?

I already mentioned that in another mail - you may need to write a new 
DBusTransport variant that uses named pipes or Windows messages. That 
would be cleaner and faster anyway. Or figure out how to define the TCP 
stuff, I'm not sure how the X server defines it if there are multiple X 
servers, but it could work in the same way perhaps.


More information about the dbus mailing list