Client- and server-side abstractions for HTTP
This documentation is built with all features enabled.
client: The client-side abstractions for generating multipart requests.
server: The server-side abstractions for parsing multipart requests.
mock: Provides mock implementations of core
servertraits for debugging or non-standard use.
hyper: Integration with the Hyper HTTP library for client and/or server depending on which other feature flags are set.
I have left a number of Request-for-Comments (RFC) questions on various APIs and other places in the code as there are some cases where I'm not sure what the desirable behavior is.
I have opened an issue as a place to collect responses and discussions for these questions on Github. Please quote the RFC-statement (and/or link to its source line) and provide your feedback there.
The client-side abstraction for multipart requests. Enabled with the
Mocked types for client-side and server-side APIs.
The server-side abstraction for multipart requests. Enabled with the
Chain a series of results together, with or without previous results.