net only.Expand description
Re-export of blitz_net.
Networking (HTTP, filesystem, Data URIs) for Blitz
Provides implementations of blitz_traits::net::NetProvider, which loads
the resources a document needs, and of
blitz_traits::platform::FetchProvider, which serves a guest’s fetch().
Both use one native HTTP/1.1 client, sharing its connection pool, cookie
jar, compression codecs, private cache and six connection slots per origin.
The http2 feature is reserved for the subsequent HTTP/2 transport.
Creating a native provider starts nagoya’s process background runtime and
the house client’s shared reactor if absent. Multiple providers reuse them.
Embedders do not need to enter an executor: callback requests use
nagoya::spawn, and async methods also work under nagoya::block_on.
Cookie persistence belongs to the embedder’s cookie jar. Disk caching is attached explicitly with a profile directory; no global cache path is used. On wasm32, local URL handling remains available, but this native socket transport does not provide HTTP.
Structs§
- Provider
- Document and script networking over one house client.
Enums§
Constants§
- DEFAULT_
USER_ AGENT - The
User-Agentsent when a caller does not choose one.