Aggregate Level Simulation Protocol: Difference between revisions

Content deleted Content added
GreenC bot (talk | contribs)
Removing link(s) to "Object manager": Removing links to deleted page Object manager.
 
(One intermediate revision by one other user not shown)
Line 94:
# The simulation repeats from step (1).
 
AIS includes a [[deadlock avoidance]] mechanism using null messages. The mechanism requires that the processes have exploitable [[Combinatorial search#Lookahead|lookahead]] characteristics.
 
====Object management====
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: