Revision as of 15:39, 21 August 2024 edit Joy (talk \| contribs) Autopatrolled, Administrators 158,169 edits m link term (WP:BUILDTHEWEB) ← Previous edit		Latest revision as of 05:26, 5 April 2025 edit undo Liz (talk \| contribs) Autopatrolled, Checkusers, Oversighters, Administrators 842,151 edits Removing link(s) to "Object manager": Removing links to deleted page Object manager. Tag: Twinkle
Line 162: Distributed object ownership presumes that no single simulation must own all objects in a confederation, but many simulations require knowledge of some objects. A simulation uses simulation protocol update messages to discover objects owned by other simulations. If this simulation is interested in the objects, it can ghost them (track their locations and state) and model interactions to them from owned objects. Locks implement attribute ownership. A primary function of the object management protocol is to ensure that a simulation only updates attributes for which it has acquired a lock. The [[object manager]] in the ACM manages the objects and object attributes of the owned and ghosted objects known to the ACM. Services provided by the simulation/ACM protocol are used by the simulations to interact with the ACM's attribute locking mechanism. The coordination of status, request, acquisition, and release of object attributes, between ACMs, uses the object management protocol. Each attribute of each object known to a given ACM has a status that assumes one of three values:

Aggregate Level Simulation Protocol: Difference between revisions