portal-mojo 0.2.10 → 0.2.11

package/docs/realtime.md

@@ -17,7 +17,8 @@ disable this shared provider.
 - An open socket is not ready. The client waits for `auth_required`, then sends
   `{type:'authenticate',token,prefix:'bearer'}` and becomes ready only after
   `auth_success`. An auth error closes and suspends the connection until the
-  token value changes.
+  token value changes. The exact direct admission-capacity error described
+  below is a transport refusal, not an authentication failure.
 - Heartbeat is a `ping` every 20 seconds with a 10-second `pong` deadline.
   A server-initiated `{type:'ping'}` (django-mojo 1.32+ sends one every 20
   seconds and culls a socket silent for 90) is answered at once with
@@ -25,7 +26,11 @@ disable this shared provider.
   dispatched to consumers. Answering from the message handler keeps the socket
   alive while a background tab throttles the client's own ping timer.
   Reconnect uses capped jittered backoff. Pre-accept close code 4429 enforces at
-  least 60 seconds, and focus/visibility cannot bypass that deadline.
+  least 60 seconds. The direct `{type:'error',message:'Too many connections'}`
+  admission refusal while authenticating or ready uses the same delay, even
+  when followed by a normal server close. Focus/visibility, token replacement,
+  and provider remount cannot bypass the deadline on that client. Queued frames
+  from the refused socket are ignored; recovery still requires authentication.
 - Desired topics are refcounted and replay after authentication. Operations are
   serialized because acknowledgements carry only the topic and denial is a
   generic uncorrelated `error`. Denial yields topic status `denied`; it does not
@@ -42,6 +47,12 @@ disable this shared provider.
 
 A top-level `{type:'error'}` frame is attributed in order:
 
+0. **Exact admission capacity refusal** — `message === 'Too many connections'`
+   while authenticating or ready: close and enter bounded `backoff`, without
+   dispatching an application error or declaring account access revoked.
+   Substrings, the `error` field, and wrapped application events do not match.
+   Consumers retain their independent HTTP authorization checks.
+
 1. **During authentication** — auth failure: the client closes and suspends
    until the token value changes. Surfaces through the lifecycle status only;
    no `error` event is dispatched.

package/package.json

@@ -1,6 +1,6 @@
 {
     "name": "portal-mojo",
-    "version": "0.2.10",
+    "version": "0.2.11",
     "description": "React portal toolkit for django-mojo — typed client + params store, mission-control UI, dependency-free SVG charts, admin section bundles.",
     "type": "module",
     "license": "Apache-2.0",

package/src/client/realtime.ts

@@ -241,6 +241,12 @@ export class RealtimeClient {
     private open(): void {
         if (!this.enabled || !this.token || this.suspended || this.socket) return;
         const run = this.generation;
+        // Token refresh and provider remount use this same entry point; neither
+        // may bypass a server admission deadline.
+        if (this.clock.now() < this.extendedBackoffUntil) {
+            this.scheduleReconnect(run, 0);
+            return;
+        }
         this.setLifecycle('connecting');
         let socket: RealtimeSocket;
         try {
@@ -312,6 +318,21 @@ export class RealtimeClient {
             if (typeof frame.topic === 'string') this.completeTopic(frame.type, frame.topic);
             return;
         }
+        if (frame.type === 'error' && frame.message === 'Too many connections'
+            && (this.lifecycle === 'authenticating' || this.lifecycle === 'ready')) {
+            // django-mojo's admission refusal also arrives after the challenge
+            // (or a ready-state capacity check), followed by a normal close.
+            // Fence queued frames before closing: late auth_success must not
+            // clear the deadline or make this refused socket ready.
+            this.extendedBackoffUntil = this.clock.now() + 60_000;
+            this.socket = null;
+            this.clearHeartbeat();
+            this.resetTopicConnectionState();
+            this.automaticUserTopic = null;
+            this.scheduleReconnect(run, 4429);
+            socket.close(4429, 'Connection limit');
+            return;
+        }
         if (frame.type === 'error') {
             if (this.lifecycle === 'authenticating') {
                 this.suspend('auth-failed', 4003, 'Authentication failed');