On 28. Apr 2009, at 13:42, Juan Hernando wrote: > Hi Stefan, > > Thanks for the quick answer > >>> 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. > Sorry, but I don't find it. My copy of the programming guide is > version > 1.3.17 (0.6RC1), do I have to download a more recent one?
Yes: - 1.5.3 Jan 13, 2009 Added Section 7 > >> Between which entities (node, pipe, net::Object) do you want to >> communicate? > I guess they will be net::Object but without having read the > documentation I'm not really sure. You'll need the net::NodeID to which you want to send the packet. If you're using Objects, the object knows its session (when mapped), which knows its local node, whose NodeID you can send to another node. The local (listening) node on the other side can connect to the other node using net::Node::connect( NodeID ). Then you simply send from the remote node using Object::send( node, ObjectPacket ). The net::Barrier code gives a nice example for this. HTH, Stefan. _______________________________________________ eq-dev mailing list [email protected] http://www.equalizergraphics.com/cgi-bin/mailman/listinfo/eq-dev http://www.equalizergraphics.com
