spinframework / spinframework/spin
Add WebSocket support via a plugin
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 6.5k
- Forks
- 310
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 24
Description
When developing spin-webrtc, I found I needed a way to maintain a persistent client-server connection to allow the server to send events to the client asynchronously. My solution was to pair Spin with websocket-bridge, which allows a serverless app to send events to clients via a persistent WebSocket.
Since this kind of "push notification" mechanism has been requested by others (here for example), I thought I'd float the idea of making websocket-bridge deliverable as a Spin plugin to make it easier to use them together. Later, if that proves popular, we could consider making websocket-bridge more robust for production use.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the linked spin-webrtc and websocket-bridge projects, then investigate how Spin plugins are delivered. Done would mean an agreed plugin integration that supports persistent WebSocket connections and asynchronous server-to-client events; the issue names no files, tests, or implementation entry point.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust, wasm
- Domain
- networking
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100