From: Jaime A L. <rub...@an...> - 2007-04-06 23:18:56
|
Kristoffer Lundén wrote: > On 3/19/07, Sjoerd Simons <sj...@sp...> wrote: >> Yeah.. If your bindings have some function which indicates that there is some >> data available, it's trivial.. >> > > Well the socket knows when there's read data available, just as with > selects. Looks like it could listen to that, meaning no problem at > all. > >> So sync return in the thread you start them in, but async run them in the dbus >> thread or does it spawn another one ? >> > > Every async call must by definition run in it's own thread, otherwise > it's not very async :). The actual message passing is in one single > thread so there's no race conditions though. > > -- Kristoffer Hi there. Any news? -- Posted via http://www.ruby-forum.com/. |