Flyology HTTP Guide Choose the lifecycle that your application owns. The client owns an origin and a bounded transport pool. An EventSource retains parser and reconnect state across requests. The server owns accepted connections and borrows each application exchange. Client exchanges, EventSource reads, and low-level HTTP/1.x reads can compose with other Flyology operations. The identifier guide derives the values that these lifecycles require from complete URI, IRI, and URL inputs.
01 / CLIENT Make outbound requests Configure one origin for HTTP/1.1, HTTP/2, or HTTP/3. Consume bounded responses, then shut down the pool. Open the client guide 02 / SSE Consume server-sent events Read bounded event streams, retain reconnect state, or compose a read across HTTP/1.1, HTTP/2, and HTTP/3. Open the SSE guide 03 / HTTP/2 Select HTTP/2 Configure client negotiation, or serve a routed application through ALPN or cleartext prior knowledge. Open the HTTP/2 guide 04 / SERVER Serve HTTP applications Own connections, route decoded paths, compose middleware, stream responses, and set admission limits. Open the server guide 05 / OPERATIONS Compose low-level HTTP reads Start request-head and body operations. Wait for them with timers, gates, cancellation, and other Flyology operations. Open the operations guide 06 / IDENTIFIERS Parse URI, IRI, and URL inputs Choose RFC or WHATWG semantics. Inspect normalized components, resolve references, and derive HTTP origins and targets. Open the identifier guide i These guides assume a prepared Flyology runtime. If the native and lightweight task lanes are unfamiliar, begin with the Flyology Runtime guide . The separate flyology_iri crate has no runtime dependency.