Skip to content

Describe sessions and registration more precisely - #173

Merged
michaelarnauts merged 1 commit into
masterfrom
docs-sessions
Oct 20, 2026
Merged

michaelarnauts merged 1 commit into
masterfrom
docs-sessions

Conversation

@michaelarnauts

Copy link
Copy Markdown
Owner

Updates docs/PROTOCOL.md:

  • Sessions: the bridge has 3 session slots, shared by the LAN and the cloud connection, so up to 3 clients can be logged in at the same time (the old text said only one). OTHER_SESSION is only returned when all slots are taken, with the name of the least recently active client in devicename. Requests that need a session, sent without one, get NOT_ALLOWED.
  • resumed: when it is set (a session with the same UUID moving to a new connection, or StartSession again on the same connection).
  • RegisterApp: an invalid UUID gets BAD_REQUEST; at most 16 apps are kept, the least used one is dropped when the list is full.
  • DeregisterApp: can remove any app, also the client's own (its session is then closed); an unknown UUID gets BAD_REQUEST.
  • Keep-alive: every message from the client counts as activity, also KeepAlive/NoOperation; a session without activity for 90 seconds is closed.

Documentation only.

🤖 Generated with Claude Code

The bridge has 3 session slots, so more than one client can be logged in.
Also describe when OTHER_SESSION and resumed are set, the limit of 16
registered apps, DeregisterApp, and the session idle timeout.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@michaelarnauts
michaelarnauts merged commit 0031176 into master Oct 20, 2026
4 checks passed
@michaelarnauts
michaelarnauts deleted the docs-sessions branch October 20, 2026 12:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant