HTTPClientRequest - multipart/form-data Support about vibe-http HOT 2 OPEN

There is currently no high-level implementation for this, so the request body would have to be composed manually. I initially thought there was an implementation, but that was just some e-mail composition code ("multipart/mixed", "multipart/alternative", "multipart/related") that we are using internally. The API of that isn't really suitable for use with the HTTP client, though, so it doesn't make much sense to take that.

As for writePart, it has been too long since it has been added like that and I honestly didn't even know it existed. However, as is, it doesn't look like a useful approach - I'd remove it together with the MultiPart struct. As a baseline, I'd probably go for something that writes everything at once, such as writeMultiPartForm(FormFields form_fields, FilePartFormFields files) (consistent with vibe.inet.webform.parseMultPartForm), or writeMultiPartForm(DictionaryList!MutiPartFormField fields), where MultiPartFormField is a TaggedUnion of union { string text; FilePart file; }.

vibe.inet.webform.FilePart may need a little overhaul for that (the tempPath member doesn't have a fitting name for this use case and it might be desirable to pass a generic input range instead), but as long as that can be done as incremental improvements, this could be a separate undertaking. The core implementation of all of this should also be in vibe.inet.webform.

Contributions here are certainly welcome!

from vibe-http.

I made two initial PRs, both in their early stage of development. Between the original RFCs and Vibe's own architecture, there's a lot going on, so I wanted to get some early feedback to make sure I'm on the right path and not too far off track.

from vibe-http.