Issue with _dbus_write_socket on windows

[Thiago Macieira]

Timothy Vismor wrote:
>Never needed to do that specific operation, but it seems that a simple
>solution could be to use named shared memory. When a process grabs
>the DBus mutex, it could write relevant address information to a well
>known block of named shared memory. When you release the
>mutex, you also release the shared memory block. If a process
>fails to grab the mutex, it could read the required information from
>shared memory.

That's exactly the X11 solution :-)

Only that the "block of shared memory" is called "X11 selection" and isn't 
shared memory.

-- 
  Thiago Macieira  -  thiago (AT) macieira.info - thiago (AT) kde.org
    PGP/GPG: 0x6EF45358; fingerprint:
    E067 918B B660 DBD1 105C  966C 33F5 F005 6EF4 5358
-------------- 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/20061118/2b2c65e2/attachment.pgp