D-Bus spec issue (Was Re: Windows DBus shared memory name depends on _DEBUG?)
thiago at kde.org
Fri Oct 8 10:56:42 PDT 2010
On Friday 8. October 2010 16.20.38 Ralf Habacker wrote:
> the following should be completly in a author note ?
No, it should not be in the spec at all. I just forgot to mark where the
suggestion ended. It ended where "Note:" below begins.
> > Note: I think the X selection atom should include the user's ID (UID),
> > not the username. We can change this and simply set both selections
> > until D-Bus 1.6.
> > The above makes it so that the X selection& property mechanism is
> > authoritative necessary and sufficient condition: the absence of the
> > information means the server is definitely not running (right now, at
> > least) and its presence means the server is definitely running.
> > The file in $HOME is not authoritative: it's a way for an implementation
> > to perform a connection without consulting the X server or running
> > dbus-launch. The presence of the file is only a necessary condition: if
> > the server is running, the file is present and contains correct
> > information. However, the file may be present and the server may not be
> > running (e.g., stale file). That's why failing to connect to the socket
> > should not be a fatal error.
> > I also wrote it in such a way that implementations are not allowed to
> > query for whether the server is running.
Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org
Senior Product Manager - Nokia, Qt Development Frameworks
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
Size: 190 bytes
Desc: This is a digitally signed message part.
More information about the dbus