On 30. Apr 2014, at 6:55, cpapado [via Software] <[email protected]> wrote:
> I've been going through EQ's source code and it seems that everything is > handled by sending messages directly to the server node. Not everything. Object map requests often go to the application thread (Framedata, ...), and so do events. > i'm a bit fuzzy on how messages are routed past that point. How would I go > about: > a) Transmitting a custom command from the application node to all render > nodes > b) Transmitting a custom command from a single render node back to the > application node > > For (b) it seems that through the config I can get a pointer to the > application node through an experimental API (co::NodePtr > getApplicationNode()). Is this safe to do so? Is the proper way to achieve > (a) just sending the message to the Server? We have not formalized a way to send commands in both directions. Obviously it is possible to do so. The formalized communication channels are the FrameData for a), which has the benefit of being latency-correct. For b), the formalized way is Config::sendEvent(). Any other way might change in future versions, but I am certain that we'll retain the functionality. That said, getApplicationNode is safe to use for b). The other way is a bit more complex. LocalNode::getNodes() gets you all connected nodes, including the server and any potential other Collage entities (admin interface, other communicators). The safest way is probably sending an event from Node::configInit and configExit and let the application track this list itself. HTH, Stefan. -- http://www.eyescale.ch https://github.com/Eyescale/ http://www.linkedin.com/in/eilemann signature.asc (858 bytes) <http://software.1713.n2.nabble.com/attachment/7585416/0/signature.asc> -- View this message in context: http://software.1713.n2.nabble.com/Communicating-information-FROM-the-rendering-code-to-the-application-logic-tp7585385p7585416.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
