Fork me on GitHub
#aleph
<
2018-11-07
>
ricardo.ekm16:11:19

Hi, we're trying to convert a ring->jetty app to ring->aleph app

ricardo.ekm16:11:32

we're using core.async and not so familiar with Manifold

ricardo.ekm16:11:45

we've checked this snippet in the docs

ricardo.ekm16:11:47

(s/take! (s/->source

ricardo.ekm16:11:15

could someone please clarify what this is doing? does it has the risk to block the thread or any performance impact?

ricardo.ekm19:11:56

We tested it doesn't block the java thread. The performance seems ok, we're doing further testing.

ricardo.ekm18:11:39

one more question what targetUtilization in the connection pool mean?

ricardo.ekm18:11:51

is it the initial open connections?

ricardo.ekm18:11:05

(in connection pool)

ricardo.ekm19:11:45

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?

ricardo.ekm19:11:14

Just found d/on-realized 🙂