Expand description
Instructions of components including client, affix, request, response, task, utils.
§OverView
client contains some methods to execute Request as Future;
utils is a collection of useful tools like hash get now time stamp now and other stuff;
the others, as the file name suggests, serve as component in integration
Modules§
- affix
- This module contains structs that adjusts Task before consume it
- body
- Contains some data structure that related to the content of HTTP
- client
- the Client that asynchronously executes Request,
- couple
- A joints of a Task and Affix in practice, it is used to reproduce a Request
- info
- A structure that carries basic meta-data, including its origin, stime stamp, privilege, encoding and so on.
- parsed
- The result of parser when parsing Response
- proxy
proxy - A proxy that will re-route the request to
Note that it currently supports
HTTP - request
- This module contains structs related to HTTP requests, notably the Request type itself as well as a builder to create requests. Typically you’ll import the http::Request type rather than reaching into this module itself.
- response
- HTTP response types.
- task
- This module contains structs related to HTTP requests,
- utils
- some utilities that useful and convenience for dealing with data flow.
- xpath
xpath - implement the xpath for the response more to see Response::xpath
Structs§
- Bytes
- A cheaply cloneable and sliceable chunk of contiguous memory.
Enums§
- Poly
- fundamental data struct
Traits§
- Buf
- Read bytes from a buffer.