Welcome to the
This crate is the primary dependency for building a trillium app or library. It contains a handful of core types and reexports a few others that you will necessarily need, but otherwise tries to stay small and focused. This crate will hopefully be the most stable within the trillium ecosystem. That said, trillium is still pre 1.0 and should be expected to evolve over time.
To get started with this crate, first take a look at the
guide, then browse the docs for
At a minimum to build a trillium app, you’ll also need a trillium runtime adapter.
Result::Okor returns the
Connwith a 500 status.
Option::Someor returns the
Macro for implementing Handler for simple newtypes that contain another handler.
A convenience macro for logging the contents of error variants.
The trillium representation of a http body. This can contain either
Vec<u8>content, or a boxed
A Trillium HTTP connection.
The name of a http header. This can be either a
KnownHeaderNameor a string representation of an unknown header.
HeaderValuerepresents the right hand side of a single
A header value is a collection of one or more
HeaderValue. It has been optimized for the “one
HeaderValue” case, but can accomodate more than one value.
Trillium’s header map type
This struct represents information about the currently connected server.
Provides support for asynchronous initialization of a handler after the server is started.
A handler for sharing state across an application.
A short nonehaustive enum of headers that trillium can represent as a u8. Use a
KnownHeaderNamevariant instead of a &’static str anywhere possible, as it allows trillium to skip parsing the header entirely.
HTTP request methods.
HTTP response status codes.
The version of the HTTP protocol in use.
The building block for Trillium applications.
Constructs a new
Statehandler from any Clone + Send + Sync + ’static. Alias for
A HTTP protocol upgrade