On 28. Apr 2009, at 13:22, Juan Hernando (via Nabble) wrote:
> I've been reading the documentation for the distributed objects, > however > I think that the implementation of this mechanism using them is > going to > be bit cumbersome because I want to decouple Equalizer specific stuff > from the rest as much as possible. I guess so to. > Before getting hands on I'd appreciate very much any hint about > whether > there is another kind of communication or signalling mechanism that > can > run asynchronously to the main rendering loop, similar to remote > method > invokation or signal broadcasting, and where should I start looking in > the reference. > > In the meantime I'll start looking at the command queues and packets > to > see if that's what I'm looking for. That's the right point. You can derive you own packets and commands, and register a command handler and/or queue with it. The receiving node will dispatch it to the right queue and method, where you can implement your reaction. This process is described in section 7 of the programming guide, and used internally a lot. Between which entities (node, pipe, net::Object) do you want to communicate? Best, Stefan. -- View this message in context: http://n2.nabble.com/Is-asynchronous-signalling-between-nodes-possible--tp2732765p2732790.html Sent from the Equalizer - Parallel Rendering mailing list archive at Nabble.com.
_______________________________________________ eq-dev mailing list [email protected] http://www.equalizergraphics.com/cgi-bin/mailman/listinfo/eq-dev http://www.equalizergraphics.com
