This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2023-02-24
Channels
- # announcements (3)
- # babashka (47)
- # beginners (40)
- # biff (21)
- # calva (12)
- # cider (2)
- # clj-kondo (31)
- # cljsrn (8)
- # clojure (14)
- # clojure-berlin (2)
- # clojure-conj (1)
- # clojure-dev (24)
- # clojure-europe (84)
- # clojure-italy (8)
- # clojure-nl (1)
- # clojure-spec (1)
- # clojure-sweden (2)
- # clojure-uk (2)
- # clojurescript (34)
- # clr (3)
- # community-development (1)
- # cursive (14)
- # datalevin (8)
- # datomic (5)
- # defnpodcast (2)
- # dev-tooling (1)
- # etaoin (4)
- # events (3)
- # fulcro (26)
- # graphql (3)
- # honeysql (6)
- # hyperfiddle (45)
- # lsp (40)
- # malli (1)
- # missionary (1)
- # nbb (18)
- # podcasts-discuss (1)
- # reagent (8)
- # reitit (2)
- # releases (2)
- # ring-swagger (1)
- # scittle (78)
- # shadow-cljs (96)
- # vim (7)
- # xtdb (3)
Hey all, I have got a nasty bug I am trying to debug here...and a silly question about xt/listen - if I have two xt/listen listeners in two namespaces, would they each receive a copy of all the indexed XTDB events?
In other words, it is not a shared resource that is exhausted by one xt/listen , correct?
> if I have two xt/listen listeners in two namespaces, would they each receive a copy of all the indexed XTDB events?
Hey @U0C8489U6 I'm not an expert on how xt/listen works exactly under the hood (yet!), but following @U0GE2S1NH’s work to expand the docstring in https://github.com/xtdb/xtdb/issues/1844 I feel quite confident responding with 'yes'