This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-11-07
Channels
- # aleph (15)
- # beginners (186)
- # boot (11)
- # bristol-clojurians (1)
- # clara (1)
- # cljdoc (2)
- # cljs-dev (5)
- # clojure (57)
- # clojure-austin (1)
- # clojure-dev (87)
- # clojure-italy (7)
- # clojure-spec (5)
- # clojure-uk (56)
- # clojurescript (18)
- # cursive (29)
- # data-science (10)
- # datomic (84)
- # duct (83)
- # figwheel-main (4)
- # fulcro (42)
- # jobs (3)
- # lambdaisland (2)
- # off-topic (28)
- # parinfer (3)
- # portkey (3)
- # re-frame (28)
- # reitit (7)
- # remote-jobs (8)
- # shadow-cljs (29)
- # spacemacs (30)
- # specter (6)
- # sql (8)
- # tools-deps (60)
Hi, we're trying to convert a ring->jetty app to ring->aleph app
we're using core.async and not so familiar with Manifold
we've checked this snippet in the docs
(s/take! (s/->source
could someone please clarify what this is doing? does it has the risk to block the thread or any performance impact?
We tested it doesn't block the java thread. The performance seems ok, we're doing further testing.
one more question what targetUtilization in the connection pool mean?
is it the initial open connections?
(in connection pool)
Sorry for the questions flood, what's the best way to deal with Aleph HTTP client + core.async. We'd like when the HTTP request is completed, put the response in a core.async channel. Does manifold deref (@) block the thread? is there a way to implement a callback function when the request is completed?
Just found d/on-realized 🙂