- multipart-stream-rs VS fullstack-rust
- multipart-stream-rs VS paperoni
- multipart-stream-rs VS nym
- multipart-stream-rs VS milli
- multipart-stream-rs VS roaring-rs
- multipart-stream-rs VS tusd
- multipart-stream-rs VS roux-stream
- multipart-stream-rs VS mpart-async
- multipart-stream-rs VS bonsaidb
- multipart-stream-rs VS letter_box
Multipart-stream-rs Alternatives
Similar projects and alternatives to multipart-stream-rs
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
multipart-stream-rs reviews and mentions
-
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.
Stats
scottlamb/multipart-stream-rs is an open source project licensed under Apache License 2.0 which is an OSI approved license.
The primary programming language of multipart-stream-rs is Rust.
Popular Comparisons
Sponsored