Replication Summary

• Introduction
• Classes And Class IDs
• Adding The Nodes
• Entering Zoidmode
• The Announcement
• Handling Node Events
• Deleting The Server Nodes
• Extended Object Information
• Replication Summary

Summary

This sums up all needed steps to object replication:

• Step 1: Implement Zoidmode callbacks in client and server

  Server needs ZCom_Control::ZCom_cbZoidRequest() to return true, client needs ZCom_Control::ZCom_cbZoidResult() to see the result of the Zoidlevel change.

• Step 2: Register classes on client and server

  With ZCom_Control::ZCom_registerClass() you have to register classnames. Client and server need an identical set of registered classes otherwise they won't be able to operate together.

• Step 3: Create a node object for each game object

  ZCom_Node *node = new ZCom_Node(); 
  

  needs to be executed for each gameobject. Each gameobject gets it's own node.

• Step 4: Register the node object with the client/server

  Call one of these functions:

  node->registerNodeUnique();
  node->registerNodeDynamic();
  node->registerNodeByTag();
  

• Step 5: Depending on replication mode, implement callbacks on client

  Unique replication doesn't need a callback. Dynamic and tag replication need ZCom_Control::ZCom_cbNodeRequest_Dynamic() or ZCom_Control::ZCom_cbNodeRequest_Tag(). Inside these callbacks an object of the requested class needs to be created and it's node needs to be registered with the client.

• Step 6: Deleting the object

  When the object gets deleted on the server, just delete the ZCom_Node object with it. Clients will get notified through an event.

• Step 7: Monitor nodes for events

  At least on the client, nodes need to be periodically checked if the object on the server has been deleted.

• Step 8: Enter a Zoidlevel

  On the client, call ZCom_Control::ZCom_requestZoidMode() on an established connection to enter a Zoidlevel. Once the server callback grants the request, replication will start.

---