Support returning MultiPart as a server reply about multipart HOT 4 CLOSED

How about an adapter that implements Read? With multipart::client::lazy::Multipart you can build your multipart body then call .prepare() which returns a type that implements Read, that you should then be able to return as your response body, or copy out to your response, depending on what HTTP framework you're using.

from multipart.

That might work, but it still sounds complicated. Could you explain why tying the construction of the body of the HTML request is so strongly tied to a Request or a Client? Is that because of streaming?

from multipart.

It's primarily to ensure that the right header is supplied with the request. The multipart boundary that separates each field in the body has to be supplied in the Content-Type header of the request, and each HTTP framework does headers slightly differently. This approach has better ergonomics for the common case where you're constructing the multipart body in the process of submitting a request. Otherwise it would be easy to forget to supply the boundary with the request and would cause difficult to debug errors on the server side.

I've done a different approach in src\local_test.rs where I have a mock implementation of HttpRequest that simply writes the request to a Vec and stores the boundary. I could extract this to the library proper but I didn't see the utility in it outside of testing.

from multipart.

Thanks for explaining everything!

I took a different approach for my problem now, so this is not required for me anymore and I think my use case was rather esoteric. I would suggest you do not pull the code out until the next one with a similar problem comes around. Closing the issue for now.

from multipart.