aleph

ricardo.ekm 2018-11-07T16:55:19.004600Z

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

ricardo.ekm 2018-11-07T16:55:32.005100Z

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

ricardo.ekm 2018-11-07T16:55:45.005500Z

we've checked this snippet in the docs

ricardo.ekm 2018-11-07T16:55:47.005600Z

(s/take! (s/->source

ricardo.ekm 2018-11-07T16:56:15.006200Z

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

ricardo.ekm 2018-11-07T16:58:10.006300Z

ricardo.ekm 2018-11-07T16:58:18.006700Z

https://aleph.io/aleph/literate.html#aleph.examples.http

ricardo.ekm 2018-11-07T18:45:39.007200Z

one more question what targetUtilization in the connection pool mean?

ricardo.ekm 2018-11-07T18:45:51.007500Z

is it the initial open connections?

ricardo.ekm 2018-11-07T18:48:05.007700Z

(in connection pool)

ricardo.ekm 2018-11-07T19:02:45.009800Z

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.ekm 2018-11-07T19:03:56.009900Z

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

ricardo.ekm 2018-11-07T19:12:14.010300Z

Just found d/on-realized 🙂

ricardo.ekm 2018-11-07T19:12:36.010400Z