How tjmers/builder works
Builder is a Rust backend framework for serving HTTP over platform-specific TCP sockets. The principal runtime path is the listener framing incoming bytes, the server parsing and routing each request to a registered handler, and response construction producing bytes for the listener to send. The graph also preserves the documented Linux/Windows socket implementations and the response-body helpers. Several listener/server internals are unsampled, so only relationships visible in excerpts, the source index, or README are shown; no storage or benchmark machinery is included.
Main entry points: tcp_listener.rs Listener API · server.rs Server routing · http_response.rs Response builder · windows.rs Windows sockets
Components 13
HTTP Routing
- Server routing
src/server.rs - HTTP parser
src/http_request.rs
TCP Transport
- Request framing
src/tcp_listener.rs - Listener API
src/tcp_listener.rs - Linux sockets
src/tcp_listener/linux.rs - Windows sockets
src/tcp_listener/windows.rs
Response Content
- Response builder
src/http_response.rs - HTTP statuses
src/data/http_response_status_codes.rs - Text payloads
src/text.rs - Image payloads
src/image.rs
Runtime Support
- Client address
src/ip_address.rs - Logging
src/logger.rs
Other components
- Framework user
Connections 11
- Framework user → Server routing: registers routes
- Server routing → HTTP parser: parses requests
src/server.rs - Server routing → Response builder: builds responses
src/server.rs - Server routing → Listener API: uses listener
src/server.rs - Listener API → Request framing: frames requests
src/tcp_listener.rs - Linux sockets → Listener API: implements sockets
README.md - Windows sockets → Listener API: implements sockets
README.md - Windows sockets → Listener API: dispatches handler
src/tcp_listener/windows.rs - Response builder → HTTP statuses: uses status codes
src/http_response.rs - Response builder → Text payloads: formats text
src/http_response.rs - Response builder → Image payloads: formats images
src/http_response.rs