On 5. May 2014, at 6:26, cpapado <[email protected]> wrote:
> I'm also trying to implement the opposite channel of communication (from a > render node back to the main app node). My current implementation utilizes > collage custom commands. If I want to utilize the same command id for for > bidirectional communication on the app node (from the window or pipe level > back to the config for example) I run into an issue where I try to register > two different command handlers on one local node for the same command ID. Correct, one for the 'to' channel to all render nodes, one for the 'back' channel from the local render node. > So > i thought I would try to use co::Object messaging instead. Why so complicated? You could either use a different command id (+1, or a new UUID) or Config::sendEvent. > However, I am not able to figure out how to send the same message to > multiple co::Object instances simultaneously. The API that I am seeing > (co::Object::send()) only allows for sending a message to a single instance > (or all instances) of an Object on a single node. Is there a way to do > "multi-cast" node sending (basically generating an ObjectOCommand with > multiple object instances on multiple nodes are the recipients)? I guess nobody needed it so far. A send( nodes, cmd ) would be easy enough to implement. Please open a ticket if you still need it. If you feel up to it, a pull request with the implementation would be even better. Cheers, Stefan. PS: Noticed your email address - are you working on the RealityDeck? I heard some rumours that you're using Equalizer and would love to see some pictures. -- http://www.eyescale.ch https://github.com/Eyescale/ http://www.linkedin.com/in/eilemann
signature.asc
Description: Message signed with OpenPGP using GPGMail
_______________________________________________ eq-dev mailing list [email protected] http://www.equalizergraphics.com/cgi-bin/mailman/listinfo/eq-dev http://www.equalizergraphics.com
