Open
Conversation
Control mode allows multiplexing exec operations over a single persistent WebSocket per sprite (via /control endpoint), avoiding the overhead of opening a new WebSocket per command. Key features: - Opt-in via control_mode: true on the client - Graceful fallback to direct WebSocket on 404 - Per-sprite support caching via ETS to avoid repeated 404s - Connection pooling with checkout/checkin and auto-drain
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
/v1/sprites/{name}/control), matching Go/JS/Python SDK implementationscontrol_mode: trueon the client; gracefully falls back to direct per-command WebSocket if the server returns 404Test plan
test123(control supported — uses multiplexed WebSocket)testandtest1234(control not supported — falls back to direct WebSocket)mix testsuite passes (34/34, excluding pre-existingSprites.hellotest)