This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-06-02
Channels
- # aleph (5)
- # beginners (112)
- # boot (137)
- # cider (10)
- # cljs-dev (36)
- # cljsrn (2)
- # clojure (118)
- # clojure-argentina (1)
- # clojure-berlin (1)
- # clojure-brasil (3)
- # clojure-dev (4)
- # clojure-italy (2)
- # clojure-nl (13)
- # clojure-russia (23)
- # clojure-spec (5)
- # clojure-uk (53)
- # clojurescript (344)
- # clojutre (1)
- # core-async (65)
- # cursive (9)
- # datascript (7)
- # datomic (28)
- # devops (1)
- # emacs (16)
- # events (1)
- # jobs (5)
- # keechma (18)
- # lumo (56)
- # off-topic (7)
- # om (3)
- # onyx (14)
- # protorepl (21)
- # re-frame (3)
- # reagent (20)
- # ring (12)
- # ring-swagger (9)
- # specter (17)
- # unrepl (14)
- # vim (14)
- # yada (22)
isaac: The Ring spec predates the recent popularity of namespaced keywords.
It’s something I’m planning to put forward for Ring 2.0, though the namespaces will be :ring.request/*
and :ring.response/*
.
I think also, ring should use deferred
to support asynchronize, instead of arity of handler
deferred from Manifold?
Manifold is a significant size - it’s larger than Ring itself.
And others might want to use different async systems.
Ring uses the lowest-common-denominator. The simplest async solution that can be translated into any other async system.
If you want to use deferreds instead of the three-arity syntax, then it’s just three lines of middleware away.
actually, I like more async, I use promise-chan support asynchronization in my app internally. 🙂
Adding promise-chan support is also just a middleware away 🙂