An asynchronous HTTP server written in Common Lisp for high-performance web applications.
Wookie is an asynchronous HTTP server written in Common Lisp that handles concurrent connections without blocking. It provides a high-performance alternative to traditional synchronous servers, particularly useful for I/O-intensive web applications. The project evolved from an attempt to port Hunchentoot to async but became its own distinct implementation.
Common Lisp developers building web applications who need asynchronous, non-blocking HTTP server capabilities. It's particularly valuable for those working on high-concurrency services or I/O-bound applications.
Developers choose Wookie for its pure Common Lisp implementation of asynchronous HTTP serving, offering better performance for concurrent connections than traditional synchronous servers. Its divergence from Hunchentoot provides a specialized async-first approach rather than just an async port.
Asynchronous HTTP server in common lisp
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Handles concurrent connections efficiently without blocking, improving throughput for I/O-bound web applications as highlighted in its asynchronous architecture focus.
Built entirely in Common Lisp, leveraging the language's strengths for server development, making it a natural choice for Lisp-centric projects.
The documentation site is built on Wookie itself, serving as a practical reference implementation and demonstrating real-world usage, as noted in the README.
Offers dual licensing under Wookie-MIT and standard MIT, providing humorous or straightforward options to suit different compliance needs.
Explicitly in beta, meaning it may have bugs, incomplete features, or breaking changes, making it unreliable for critical production deployments.
As a Common Lisp project, it has a smaller community and fewer integrations compared to HTTP servers in more popular languages, limiting support and tooling.
Requires understanding of async patterns in Common Lisp, which can add development overhead and steeper learning curve versus synchronous servers.