This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-02-04
Channels
- # aatree (5)
- # admin-announcements (37)
- # alda (1)
- # announcements (4)
- # architecture (1)
- # aws (3)
- # beginners (82)
- # boot (230)
- # braid-chat (14)
- # cider (48)
- # cljs-dev (8)
- # cljsrn (31)
- # clojars (47)
- # clojure (72)
- # clojure-austin (2)
- # clojure-russia (396)
- # clojurescript (72)
- # community-development (3)
- # component (6)
- # core-async (6)
- # cursive (26)
- # datomic (42)
- # emacs (6)
- # events (35)
- # hoplon (57)
- # immutant (3)
- # jobs (2)
- # jobs-discuss (10)
- # ldnclj (16)
- # luminus (2)
- # off-topic (50)
- # om (181)
- # parinfer (285)
- # proton (68)
- # re-frame (19)
- # reagent (2)
- # ring-swagger (23)
- # yada (36)
Morning.
is there a pattern/lib/datastructure to handle rapidly changing hash sets? I've got two incoming streams of data. One a stream of channels, and the other a stream of packets for those channels... I receive a channel, and then shortly after I expect a data packet for that given channel. Currently I'm just storing the channels in an atom containing a map and doing swap! constantly.
so you get a channel (with an id of some sort?) and then a packet for the channel (also with an id for channel?) put the packet on the channel, then what happens to the channel ? close or await further packets ?
atom/swap! doesn't seem unreasonable to me... agents could also be useful, though unless you need the STM stuff they probably aren't doing anything for you over atom/swap!
though agents do the thread-pool stuff themselves, so that may be useful
and if you are on cljs rather than clj then there is only atom
agents ?