cl-async
wookie
Our great sponsors
| cl-async | wookie | |
|---|---|---|
| 2 | 2 | |
| 265 | 186 | |
| - | - | |
| 4.9 | 10.0 | |
| 5 months ago | about 1 year ago | |
| Common Lisp | Common Lisp | |
| MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
cl-async
-
Subprocesses in CL
You could take a look at https://lisp-journey.gitlab.io/blog/common-lisp-async-web-scraping/ and https://github.com/orthecreedence/cl-async
-
Asynchronous web programming in CL?
As for the library offering the async primitives, cl-async seems to be comparable with asyncio - however, it's based on libuv (a different event loop) and I'm not sure whether it's advisable or idiomatic to mix it with Woo.
wookie
-
Why Turtl Switched from Common Lisp to JavaScript
In this case, an async (via cl-async) application served by an async app server (http://wookie.lyonbros.com/), so async all the way down using evented I/O vs an async server (Woo) that farms out all requests to a synchronous thread pool.
-
Asynchronous web programming in CL?
cl-async's web server companion is https://github.com/orthecreedence/wookie, by the same author.
What are some alternatives?
woo - A fast non-blocking HTTP server on top of libev
cl-coroutine - Cl-coroutine is a coroutine library for Common Lisp. It uses cl-cont continuations library in its implementation.
cl-tbnl-gserver-tmgr - Hunchentoot Gserver based taskmanager
doc - Flexible documentation generator for Common Lisp projects.
bordeaux-threads
quick-patch - Easily override quicklisp projects without using git submodules
core-cl - (experimental, deprecated) Common Lisp core for Turtl. The goal is to put all logic in lisp, and embed in other runtimes (Node-webkit, Android, iOS). Note that most desktop/mobile browsers now support the features that turt/js needs to run, so turtl/core has reached the end of its life. It remains as a reference or as a great place to pick up from if lisp is needed in the future.