Every value on this page comes from a real call to the OddSockets platform in this browser session.
Live response from POST /api/apikeys/validate on the cluster
manager, plus the worker this browser was actually assigned to.
| Status | waiting for the platform… |
|---|
Server-side channel namespace
The worker prefixes every room with the owner scope derived from the validated key,
not from anything this browser sends. A channel called room-1
is really this room on the server:
1. Publish inside the key's own namespace
Channel –. The text below is
published over the socket and the panel only updates when the platform delivers it back.
2. Try to address another tenant's namespace
The scope separator :: is reserved for the server. A client
that tries to smuggle it into a channel name is attempting to read another owner's rooms.
This button really sends that subscribe request:
–
Opens a second, independent connection using a key that was never issued, and shows whatever the platform says. A pass here means the handshake was refused.
–
Real occupancy of this key's demo channel. Open this page in a second tab and the count goes up; it is not a counter driven by a timer.