Austin Bonander

Gotham is an async framework so it's more in-line to support it in my [`multipart-async`](https://github.com/abonander/multipart-async) crate (which has admittedly languished a bit). Gotham has been discussing supporting `multipart/form-data` integrally for...

It still works with Hyper 0.10 and below. I am working on a version that supports asynchronous requests but I'm not sure if I want to publish it as a...

> is this really necessary? if anyone needs legacy support they can just use an old version of multipart, also that's why we use SemVer. The issue with having legacy...

1.x can't be the async version as it would still expose public dependencies that are not yet 1.x (`futures` and `mime`, namely). Backporting is a bit of a pain, especially...

I've been aware of the `streaming-iterator` crate for a while, but it currently does not support this use-case very well. The problem with the `StreamingIterator` trait is that it only...

Multipart is done exclusively with the `POST` verb. This is handled in `Multipart::client_request()`. As far as I can tell, your usage is correct; the error is coming from a `write()`...

Okay, I've run your test and gotten the error but there's something I don't understand. The only occurrence of that error string is `src/server/save.rs` which is *the wrong side of...

Ah, I see, it also occurs in [the `Write` impl for `&mut [u8]`](https://github.com/rust-lang/rust/blob/f338dba29705e144bad8b2a675284538dd514896/src/libstd/io/impls.rs). It's when the slice is smaller than the input data, which is... not optimal.

I stepped through this with a debugger and it doesn't seem to be Multipart's fault. The error occurs when trying to write to the network stream, after `io::copy()` has read...

Is `Multipart::with_body()` not sufficient? That just takes the boundary and a `Read` impl.