spinframework / spinframework/spin-rust-sdk
Using futures TcpStream with spin
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 35
- Forks
- 23
- Avg merge
- 37m
- Merged PRs (30d)
- 1
Description
Hello, I'm evaluating using spin for one of my applications and need it to connect to a MSSQL database, using the tiberius crate, but I'm really new to using WASM in general.
So far I've had to disable openssl because of openssl-sys not compiling and rustls didn't work either (but that's a Tiberius issue I guess?) and now I'm having issues with the TcpStream since I don't know where I could find a working async socket to use with spin that implements the traits from the futures crate (AsyncWrite and AsyncRead).
Maybe I'm just not looking in the right places...
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 by reproducing the TcpStream setup described with Spin, WASM, futures, and the tiberius crate, including the OpenSSL and rustls constraints. Determine whether the Spin Rust SDK exposes a compatible async socket or whether the limitation belongs to tiberius; done means documenting a supported path or a clearly scoped SDK change.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust, wasm
- Domain
- backend, databases, networking
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100