This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-08-17
Channels
- # arachne (1)
- # beginners (42)
- # boot (4)
- # cider (28)
- # clara (9)
- # cljs-dev (149)
- # cljsrn (5)
- # clojure (185)
- # clojure-austin (2)
- # clojure-dusseldorf (4)
- # clojure-italy (14)
- # clojure-norway (1)
- # clojure-russia (18)
- # clojure-spec (35)
- # clojure-uk (36)
- # clojurescript (78)
- # core-async (6)
- # data-science (20)
- # datomic (48)
- # emacs (1)
- # fulcro (2)
- # garden (4)
- # hoplon (47)
- # jobs (5)
- # jobs-rus (1)
- # leiningen (2)
- # lumo (12)
- # off-topic (8)
- # om (8)
- # onyx (39)
- # parinfer (19)
- # re-frame (100)
- # reagent (15)
- # ring-swagger (1)
- # sql (8)
- # vim (1)
- # yada (20)
Say, is there a variation on the core.async pub/sub stuff where my subscribers can provide a predicate that takes the topic as input and returns true
if it should be handled?
As far as I can tell the setup as-is can only dispatch on (= event-topic subscriber-topic)
, but I'd like it to dispatch on (my-predicate event-topic)
instead. One motivation for this is I want to write a fire-hose function that receives every event regardless of the topic.
@timgilbert wouldn’t it be simpler to have a mult coming off the same channel that goes into the pub?
so the pub and the mult get all the same messages, subscribing to the mult gets all messages, subscribing to the pub gets the topics you subscribe?
and I could even imagine a system where you expand on this by tracking the set of existing topics from the mult
Yeah, was just thinking about doing that