3 ms·
In this case, an async (via cl-async) application served by an async app server (http://wookie.lyonbros.com/ http://wookie.lyonbros.com/), so async all the way
by orthecreedence 5y ago
In this case, an async (via cl-async) application served by an async app server (http://wookie.lyonbros.com/ 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.
I've been asked multiple times why I "didn't just use Woo" by people who don't understand that Turtl's server was async and Woo doesn't support async.
- gibsonf1 5y agoI guess the question is what does that have to do with it? Why not just work asynchronusly with requests that hit the server with a library like lparallel with their futures? Isn't it about the response to the request?
- orthecreedence 5y ago> Isn't it about the response to the request? High level, yes. Mid/low-level, it really depends on what you're doing. If you're serving static files, sure, use Nginx/Woo. If you're running an evented CL application that deals mostly with network i/o, threading is going to be a tank when you need a hummingbird. I built cl-async/wookie as parallels for nodejs/express in common lisp.
- math-dev 5y agoOh, are you the developer mentioned in the main post? If so, I agree a lot with what you said!
- orthecreedence 5y agoI am! Turtl is my baby.
- math-dev 5y agoAwesome stuff!