Plain

Closes the underlying database (if the system is durable). The STM cannot be used beyond this call. An in-memory system should have a no-op implementation.

Creates a handle (in-memory) to refresh a stale version of an object, assuming that the future transaction is issued from the same cursor that is used to create the handle, except for potentially having advanced. This is a mechanism that can be used in live views to gain valid access to a referenced object (e.g. self access).

Creates a new in-memory transactional map for storing and retrieving values based on a mutable's identifier as key. If a system is confluently persistent, the get operation will find the most recent key that matches the search key. Objects are not serialized but kept live in memory.

Id maps can be used by observing views to look up associated view meta data even though they may be presented with a more recent access path of the model peer (e.g. when a recent event is fired and observed).

Issues a new transaction (executor), runs the function argument on it, and returns the result.

Issues a new transaction (executor), tagged with the given time referring to "now", runs the function argument on it, and returns the result.

The tagging can be used for latency based circumstances, such as scheduling OSC bundles on a sound server.