1. Flyology HTTP
  2. Guide

Begin at the lifecycle you own.

The client owns an origin and bounded transport pool. The server owns accepted connections and borrows each application exchange. Their guides keep those responsibilities separate.

01 / CLIENTMake outbound requestsConfigure one origin, build request metadata, stream bounded bodies, consume responses, and shut down the pool.Open the client guide02 / SERVERServe HTTP applicationsOwn connections, route decoded paths, compose middleware, stream responses, and size admission limits.Open the server guide