Fork me on GitHub
#core-async
<
2016-07-19
>
alexmiller13:07:16

You might want to look at pipeline-async

ska13:07:13

@alexmiller: is this a good and idiomatic example? https://gist.github.com/JacobNinja/5c98496a632e1a466cbf

fhanreich13:07:59

(@ska @alexmiller I have the same question)

ska14:07:15

@fhanreich: It's pretty hard to find docs and good examples in this area, isn't it?

fhanreich14:07:30

@ska yes. I’m struggling with it. Any recommendations (resource, etc), I’d highly appreciate it.

dominicm15:07:30

pipeline-async returns a channel, which can be closed to stop it's running. This isn't mentioned in it's docstring, can the behaviour be depended upon?

dominicm15:07:54

Looking at the source code, this just stops the processor, and shouldn't be used.

alexmiller16:07:46

@ska that looks like a pretty good gist to me. I would recommend future instead of async/go in the af. Be aware that while you are making the external request, you are tying up a thread in the (fixed size) a/go pool and can thus cause everything to block. The future thread pool can grow however so does not suffer from this issue.

alexmiller16:07:29

@dominicm the docstring does not mention the result of pipeline-async, so I would not expect to use it for anything

fhanreich19:07:10

@alexmiller Aside from the book Clojure Applied, which has been very helpful, are there any recommended resources to learn core.async (and Components) and put something (a small app) together for a beginner?

alexmiller20:07:05

Tim Baldridge has a bunch of videos that illuminate a lot of things

ska21:07:27

thanks, @alexmiller