ProtectedconstructorCurrent number of live (un-consumed, un-expired) tickets — for diagnostics/tests.
Current number of relay sessions that have not ended (ended ones, and those whose fresh connection never opened within its window, are pruned) — for diagnostics and tests.
StaticInstanceProcess-wide singleton accessor.
Consumes a ticket by id: returns its entry and DELETES it (single-use), or null if the id is
unknown or expired. Prunes expired tickets as a side effect. The proxy calls this exactly once,
during the websocket upgrade, before opening the upstream leg.
Looks up a relay session that can still take a connection, without opening one: the relay calls this at the
websocket upgrade and answers 401 on null. null when the id is unknown, the session has ended or reached its
connection limit, or neither a fresh open (unused, within its window) nor a resume (a forwarded handle) is left.
The Global Object Store is a place to store global objects that need to be shared across the application. Depending on the execution environment, this could be the window object in a browser, or the global object in a node environment, or something else in other contexts. The key here is that in some cases static variables are not truly shared because it is possible that a given class might have copies of its code in multiple paths in a deployed application. This approach ensures that no matter how many code copies might exist, there is only one instance of the object in question by using the Global Object Store.
Mints a single-use ticket authorizing ONE upstream open within its TTL window, and returns the opaque id to embed in the browser-facing proxy URL. Prunes expired tickets as a side effect.
Issues a relay session and returns its ticket id (for BuildRealtimeRelayUrl) and the moment it ends. The
session opens one fresh connection within OpenWithinSeconds, then only resumes that present a handle the relay
forwarded to it; it ends at LifetimeSeconds or MaxSessionSeconds, whichever comes first, and accepts at most
MaxConnections connections. Nothing is called on the policy here: headers are fetched per upstream open.
Decides one connection from what its first frame asks for. A fresh intent opens only the session's first connection, within its open window; a resume opens only with a handle the relay forwarded to this session. Either way the session must not have ended or reached its connection limit. A granted connection counts toward the limit; a refused one does not.
Records a resumption handle the relay is forwarding to a session's browser, so a later resume may present it. The relay calls this before the frame that carries the handle goes out. Unknown or ended sessions, empty handles and repeats are ignored; the session keeps its RELAY_HANDLE_MEMORY most recent handles.
Protected StaticgetReturns the singleton instance of the class. If the instance does not exist, it is created and stored in the Global Object Store. If className is provided it will be used as part of the key in the Global Object Store, otherwise the actual class name will be used. NOTE: the class name used by default is the lowest level of the object hierarchy, so if you have a class that extends another class, the lowest level class name will be used.
OptionalclassName: string
Process-wide, in-memory registry of one-time realtime-proxy tickets (Global Object Store backed via BaseSingleton, so the provider driver that mints and the MJAPI proxy that consumes share the SAME instance even under bundler code duplication).
Intentionally has no background timer: entries are pruned lazily on every Issue / Consume, so there is nothing to shut down and no
IShutdownablewiring is required. Tickets are short-lived and single-use — the map never grows unbounded in practice.Deliberately transport-agnostic: it stores plain data (URL + optional auth + expiry) and knows nothing about websockets or any specific provider. The proxy transport lives in MJServer; the mint logic lives in the provider driver. This is the neutral shared state between them.
It also holds relay sessions (IssueRelaySession): one ticket per realtime session that opens one fresh connection, then only resumes that present a handle the relay forwarded to that session. They live in this process's memory too, so a resume must reach the MJAPI instance that issued the session (sticky routing for REALTIME_RELAY_PATH in multi-instance deployments).