In your examples, you put a let around the reads from timeouts.
(let [_ (a/! (a/timeout 1000))] ... )
As far as i know, that is not neccessary. So your first example could be:
(defn delayed-hello-world-handler
[req]
(d/-deferred
(a/go
(a/! (a/timeout 1000))
I suspect it would, I think I was just letting the mechanics of Manifold's
let-flow macro color my judgment. Happy to accept any pull requests which
make my core.async examples more idiomatic.
On Apr 18, 2015 8:33 AM, Matthias Lange matthias.la...@gmail.com wrote:
In your examples, you put a let
Hey all,
In preparation for Clojure/West, I'm formally releasing the latest Aleph
and the libraries that surround it. Aleph 0.4.0 has been running in
production at Factual for half a year now, and across a variety of services
is handling at peak 600k HTTP requests/sec (spread across 15-20
You really hit the ball out of the park with Aleph 0.4.0's API. You have
set the standard for simplicity and power in a Clojure API with this
release as far as I'm concerned. Thank for your your contribution!
On Friday, April 17, 2015 at 5:06:30 PM UTC-4, Zach Tellman wrote:
Hey all,
In
I'd like to add Aleph to the Luminus template and I was wondering if
there's an equivalent of dev mode available for other servers where it
watches for changes in source and reloads them. I did a cursory look but
didn't spot anything like a -dev option.
On Friday, April 17, 2015 at 5:06:30 PM
Hey Dmitri,
I haven't used any sort of dev-mode before (I just update stuff in the REPL
when necessary), but it seems like something like that belongs in
middleware, not the server. The server is just calling a function, it
shouldn't care if something else is changing that function's behavior.
