Re: [g-a-devel] [Accessibility-atspi] D-Bus AT-SPI - The way forward
- From: Rob Taylor <rob taylor codethink co uk>
- To: gkraft gnome org
- Cc: "Aaron M Leventhal/Cambridge/IBM"@us.ibm.com, gnome-accessibility-devel <gnome-accessibility-devel gnome org>, accessibility-atspi-linux-foundation <accessibility-atspi lists linux-foundation org>, Mark Doffman <mark doffman codethink co uk>, kde-accessibility <kde-accessibility kde org>, accessibility-linux-foundation <accessibility lists linux-foundation org>
- Subject: Re: [g-a-devel] [Accessibility-atspi] D-Bus AT-SPI - The way forward
- Date: Thu, 06 Dec 2007 15:07:55 +0000
George Kraft wrote:
>> D-Bus case all connections made are using local unix sockets.
>
> How will a D-Bus version of AT-SPI handle sudo (local non $USER owned
> applications displaying to $DISPLAY) and remote applications ($USER and
> non $USER owned applications displaying to $DISPLAY) work?
A good question. The 'connection address' of the session bus is an
environment variable, usually setup by Xsession. So all programs run
within one Xsession will connect to the session bus for that X session,
regardless of $USER.
In terms of remote applications, there is a plain TCP transport, and
when using this authentication happens by means of tokens in the users
home directory, so it should work fine in a thin client situation.
Thanks,
Rob
> George (gk4)
>
>
>
> _______________________________________________
> Gnome-accessibility-devel mailing list
> Gnome-accessibility-devel gnome org
> http://mail.gnome.org/mailman/listinfo/gnome-accessibility-devel
--
Rob Taylor, Codethink Ltd. - http://codethink.co.uk
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]