Hello everyone! I'm porting some code over from a super-old version of EQ (1.2) to the latest and greater. In a part of my code, I had put together a couple of custom command packets (inheriting from eq::ClientPacket and co::NodePacket) which were being exchanged between my EQ server and an external application that used Collage to map a distributed object.
I'm seeing that in the 1.7 API these base classes do not exist. If anyone could provide some basic pointers on how that part of CO's functionality should be restructured, I would greatly appreciate it :). If I am understanding the headers correctly, command packets no longer exist but rather commands are spawned based on unique identifiers. Then the commands implement data streams that can be used to serialize/deserialize various information. Am I understanding this correctly? Thank you, Harris -- View this message in context: http://software.1713.n2.nabble.com/Porting-from-EQ1-2-to-EQ1-7-eq-ClientPacket-co-NodePacket-equivalents-tp7584706.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
