TeaTime Framework

Messages are placed in to a timeline and the timeline is synchronized

Control of message flow, filtering etc, controls how the world synchronizes

TeaTime: coordination

TeaParty: replication

Behavior is expressed as messages over a timeline. An object is an evolving history of its incoming messages.

Maps incoming messages to outgoing messages via methods; output is a function of inputs.

Messages belong to a timeline (TeaTime) with timing constraints. They specify when they occur in some future of the timeline.

Objects are functionally just a unique name. "Clones" are the same object name on multiple machines.

Timelines are malleable for a period of time until they are committed.

All objects belong to one 'party' and the parties are cloned across the machines.