Hi Vamsi: The atk-bridge contains the answer to both of your questions. It is both the service which adapts the in-process ATK interfaces (implemented by gail) to the out-of-process AT-SPI interfaces, exported via CORBA IPC. If you look closely at at-spi/atk-bridge/bridge.c, you will see where the connections take place.
It is also the code which registers each application with the at-spi-registryd Registry service, when the application initially starts up, via gnome_accessibility_module_init(). Here's a process-space diagram showing how apps, the AT-SPI registry, and assistive technologies communicate: http://developer.gnome.org/projects/gap/tech-docs/SPIBlockDiagram.png regards Bill On Tue, 2006-03-14 at 22:58, Vamsi wrote: > Hi List, > > I'm trying to understand how the accessibility works !! i have some > doubts regarding the same. > > 1. How does the at-spi, atk-bridge and gail communicate with each other. > do they corba(bonobo) to communicate, if yes i have not seen any > corba related code in gail then how it is passing the info to at-spi > along with atk-bridge ?? > > 2. When we launch an application on the desktop how does it registers > itself with at-spi registryd. how the communication is getting > transferred from application to at-spi ?? > > Thank You. > > -Vamsi > > > > _______________________________________________ > Gnome-accessibility-devel mailing list > [email protected] > http://mail.gnome.org/mailman/listinfo/gnome-accessibility-devel _______________________________________________ Gnome-accessibility-devel mailing list [email protected] http://mail.gnome.org/mailman/listinfo/gnome-accessibility-devel
