websockets-rs / websockets-rs/rust-websocket
Why async_connect_on requires Send on the Stream?
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 1.6k
- Forks
- 225
- PR merge metrics
- No merged PRs in 30d
Description
Can't it just be single-threaded?
56 | .async_connect_on(p4ws);
| ^^^^^^^^^^^^^^^^ `tokio_io::AsyncRead + 'static` cannot be sent between threads safely
Contributor guide
No contributing guide indexed for this repository
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 at the async_connect_on API shown in the issue and trace why the Stream requires Send. Check the surrounding connection and executor behavior to determine whether a single-threaded path is supported. Done would mean either a clearly documented limitation or tested support for the requested non-Send stream behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- networking
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100