When a new object is found that matches a node's interests, the object location component passes the metadata of the new object (its GUID, SID, and other naming attributes) to the object manager. The object manager contacts the primary object's owner (identified by its SID) directly to register the interest in the object (identified by its GUID). The primary object's node then marshals the state required for instantiating a replica on the local node. The primary object's node also periodically sends deltas of the object to each replica to keep them up-to-date. Each node holding a replica may also send updates to the object back to the primary to modify the object. In essence, this forms a 1-level distribution tree rooted at the primary object's node, and is similar to how object synchronization occurs between a server and its clients in the client-server architecture.