Expand description
Instructions of plugins including middleware, pipeline and their usage.
OverView
middleware serve as a processor between components, processes data in-and-out.
pipeline serve as the end of the data flow, data-storage happens here.
Modules
The trait that produces a Affix for extensive application. In general, it is not necessary to implement this trait, most of request does not require too much, once uri is provided, the response gives what you want. For those that do not, the trait serves as a actor to adjust
Some useful tools to serialize and deserialize components,
plugin that process data flow in and out of Actor between component.
the end of data flow, plugin that consume the extracted Entity, In general, the default
method does nothing, and customization is requird to store the data. An example:
mod that contains serialize funtion and deserialize funtion to actor parser funciton it deserializes string into actor parser when loading and serialize the parser function to string when storing, debug, or stdout
mod that contains serialize funtion and deserialize funtion to ser-de http::HeaderMap
mod that contains serialize funtion and deserialize funtion to ser-de Option variant of http::HeaderMap
mod that contains serialize funtion and deserialize funtion to ser-de http::header::HeaderName
mod that contains serialize funtion and deserialize funtion to ser-de http::HeaderValue
mod that contains serialize funtion and deserialize funtion to ser-de http::Method
mod that contains serialize funtion and deserialize funtion to ser-de http::Version
Structs
Represents a medium that handles the dataflow of App
Serve as an medium to create an instance of MiddleWare
Serve as an medium to create an instance of PipeLine
Statics
A vector of tuple which contians function name(&str) and function pointer (*const ()),