This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-07-15
Channels
- # aleph (5)
- # bangalore-clj (1)
- # beginners (53)
- # boot (1)
- # cljs-dev (327)
- # cljsrn (3)
- # clojure (16)
- # clojure-filipino (47)
- # clojure-nlp (4)
- # clojure-russia (1)
- # clojure-spec (3)
- # clojurescript (64)
- # core-async (6)
- # datomic (25)
- # hoplon (5)
- # jobs (5)
- # klipse (2)
- # lein-figwheel (2)
- # lumo (27)
- # om (2)
- # onyx (6)
- # parinfer (4)
- # pedestal (1)
- # protorepl (1)
- # re-frame (31)
- # ring-swagger (1)
- # specter (9)
- # unrepl (11)
hey guys, on thinking about using core.async for a service I’m curious about the infectiousness of channels. is there a way to prevent the spread of go blocks into consumers of my service? is it a simple as
(service/do-something-async :val then-callback)
where the service eventually just pulls a result from a channel, then invokes the then-callback
of the consumer?there's more options in jvm clojure - you can use things like put!
and <!!
etc.
ah, that’s right I forgot there’s no blocking in cljs. so at worst consumers would just know that the service works with csp and they should <!!
. i suppose that’s a little better than a callback, at least for readability
@lwhorton my talk at the last Clojure/West was on that subject: https://www.youtube.com/watch?v=096pIlA3GDo
thanks @tbaldridge ill take a look