Re: [g-a-devel] [Accessibility-atspi] D-Bus AT-SPI - The way forward

[Rob Taylor <rob taylor codethink co uk>]

Rob Taylor wrote:
> 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.


I should add, there is an issue when running applications remotely via
ssh. The preferred solution in this case is to add support to ssh for
forwarding the dbus connection and setting the envvar on the remote end,
exactly as happens with X11 and $DISPLAY now. Does AT-SPI currently cope
in this situation and if so, how?

Thanks,
Rob

> 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