fullstack-rust
multipart-stream-rs
Our great sponsors
fullstack-rust | multipart-stream-rs | |
---|---|---|
2 | 2 | |
88 | 6 | |
- | - | |
0.0 | 0.0 | |
7 months ago | over 1 year ago | |
Rust | Rust | |
Apache License 2.0 | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
fullstack-rust
-
Pooled connections to database on websocket server
This repo outlines how to make pooled connections to an SQLite database on an Http server.
-
What's everyone working on this week (17/2021)?
Allow me to share my toy-project - full stack, WebAssembly Rust application: https://github.com/vascokk/fullstack-rust
multipart-stream-rs
-
Introduction to HTTP Multipart
The article talks about multipart/form-data in particular.
Another thing one might run across is multipart/x-mixed-replace. I wrote a crate for that. [1] I didn't see a spec for it, but someone since pointed out to me that it's probably identical to multipart/x-mixed, and now seeing an example in the multer README it clicks that I should have looked at RFC 1341, which says this:
> All subtypes of "multipart" share a common syntax, defined in this section.
...and written a crate general enough for all of them. Maybe I'll update my crate for that sometime. My crate currently assumes there's a Content-Length: for each part, which isn't specified there but makes sense in the context I use it. It wouldn't be hard to also support just the boundary delimiters. And then maybe add a form-data parser on top of that.
btw, the article also talks specifically about proxying the body. I don't get why they're parsing the multipart data at all. I presume they have a reason, but I don't see it explained. I'd expect that a body is a body is a body. You can stream it along, and perhaps also buffer it in case you want to support retrying the backhaul request, probably stopping the buffering at some byte limit at which you give up on the possibility of retries, because keeping arbitrarily large bodies around (in RAM or even spilling to SSD/disk) doesn't sound fun.
[1] https://crates.io/crates/multipart-stream
-
What's everyone working on this week (17/2021)?
I find my implementation in parser.rs kind of gross, but at least it seems to work. If anyone happens to look, I'd appreciate tips for cleaning up this code.
What are some alternatives?
rust-yew-realworld-example-app - Exemplary real world app built with Rust + Yew + WebAssembly, by Function Components + Hooks, also supports desktop by Tauri.
paperoni - An article extractor in Rust
bonsaidb - A developer-friendly document database that grows with you, written in Rust
nym - Manipulate files en masse using patterns.
narcissus - API using PostgREST to query and update supabase database.
milli - Search engine library for Meilisearch ⚡️
yew-components - Material Design Components for the Yew framework
roaring-rs - A better compressed bitset in Rust
Yew-WebRTC-Chat - A simple WebRTC chat made with Yew
tusd - Reference server implementation in Go of tus: the open protocol for resumable file uploads
roux-stream - Streaming API for the Rust Reddit Client roux