Open-Awesome
CategoriesAlternativesStacksSelf-HostedExplore
Open-Awesome

© 2026 Open-Awesome. Curated for the developer elite.

TermsPrivacyAboutGitHubRSS
  1. Home
  2. Common Lisp
  3. fast-http

fast-http

Common Lisp

A fast HTTP request/response parser for Common Lisp with low-level APIs and zero memory allocation during parsing.

GitHubGitHub
363 stars37 forks0 contributors

Overview

A fast HTTP request/response parser for Common Lisp.

Use Cases

Not Ideal For

  • Projects needing a high-level HTTP client or server with built-in routing and middleware
  • Applications that require caching entire HTTP bodies in memory for batch processing
  • Teams preferring object-oriented abstractions over callback-driven APIs
  • Environments where stable, unchanging low-level APIs are essential for long-term code maintenance

Pros & Cons

Pros

Blazing Fast Parsing

Benchmarks show it parses HTTP headers 1.25x faster than a C equivalent, thanks to zero-allocation parsing and optimized structure classes, as highlighted in the performance section.

Unified Request/Response API

Handles both HTTP requests and responses with a single parser, simplifying code for bidirectional communication, as noted in the features list.

Streaming-First Design

Callback-driven approach allows incremental processing of HTTP bodies via events like body-callback, ideal for handling large or continuous data streams without memory overhead.

Memory Efficiency

Avoids storing bodies in memory by design, using pointers in callbacks and omitting :store-body options, which is crucial for high-throughput applications as mentioned in the API differences.

Cons

Complex API Surface

The callback-heavy design and low-level functions like parse-request require manual state management, increasing implementation complexity and learning curve beyond simple use cases.

Missing Convenience Features

Lacks built-in body storage and has no :force-stream option, forcing developers to handle these aspects themselves, as admitted in the comparison with http-parse.

Aggressive Error Handling

Raises errors aggressively during parsing, which can be harsh for applications needing to gracefully handle malformed HTTP messages without crashing.

Volatile Low-level APIs

The README explicitly warns that low-level APIs are likely to change, posing a risk for code relying on them and potentially causing breaking changes in future updates.

Frequently Asked Questions

Quick Stats

Stars363
Forks37
Contributors0
Open Issues5
Last commit6 months ago
CreatedSince 2014

Tags

#server-side#http#streaming-parser#network-protocols#low-level-api#http-parser#web-development#common-lisp#performance

Built With

C
Common Lisp

Included in

Common Lisp2.9k
Auto-fetched 1 day ago

Related Projects

DexadorDexador

A fast HTTP client for Common Lisp

Stars437
Forks46
Last commit6 months ago
http2http2

HTTP/2 implementation in Common Lisp

Stars51
Forks4
Last commit4 months ago
CarrierCarrier

A lightweight, async HTTP client

Stars44
Forks10
Last commit2 years ago
Community-curated · Updated weekly · 100% open source

Found a gem we're missing?

Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.

Submit a projectStar on GitHub