Reference

State Persistence Model

Look up syntax, contracts, layouts, algorithms, and exact behavior.

The state model is page-scoped and renderer-scoped. A base page definition supplies the component class or component tree, but active component instances belong to a renderer. Before a transition, the outgoing tree can serialize state; after a transition, the incoming page receives either its prior renderer-local state or a fresh instance.

State = \{(rendererId, pageId) \mapsto componentInstance\}

Per-renderer page state. The same page definition can have distinct live component instances for different users.

save outgoing page state
run outgoing unload hook
select next page for renderer
load or create renderer-local component instance
render next page shell
run incoming load/afterRender hooks

Page transition. Transitions coordinate lifecycle hooks, state persistence, active-page selection, and rendering.

This model favors explicit ownership over implicit reconciliation. The server can decide when state is saved, when it is discarded, and which renderer receives which page instance.

State Persistence Model

Continue exploring