TSXLight / docsProject documentation

Reference

Per-User Renderer Instances

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

A TSXLight instance is created with a renderer ID and registered with the PageManager. It owns the current DOM template, root component, base app wrapper, renderer ID, and the user-specific output file path or socket channel.

Ru=(Du,Cu,Pu,Ku)R_u = (D_u, C_u, P_u, K_u)
Renderer isolation. Each user renderer owns its DOM shell, component tree, active page, and callback table.

The per-user instance model is the central isolation boundary. Each user can have separate component state, callback registrations, page state, and communication, which prevents one user's rerender path from mutating another user's active page.

Server-owned components create an immediate isolation problem: a single global component tree would make every connected user share clicks and state. TSXLight routes user identity to a renderer ID, renderer ID to active page, and active page to component instance and callback table.

  • UserManager maps users to renderer IDs.
  • PageManager maps renderer IDs to active page IDs and per-page component instances.
  • Each renderer can save states before page transitions and rerender independently.
  • Settings can limit duplicate active connections per user.