This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-07-04
Channels
- # admin-announcements (14)
- # aleph (3)
- # beginners (75)
- # boot (95)
- # carry (4)
- # cider (23)
- # clojure (39)
- # clojure-android (3)
- # clojure-brasil (2)
- # clojure-dev (17)
- # clojure-gamedev (1)
- # clojure-mexico (12)
- # clojure-poland (12)
- # clojure-romania (1)
- # clojure-russia (10)
- # clojure-spec (8)
- # clojure-uk (36)
- # clojurescript (34)
- # core-async (4)
- # datomic (40)
- # emacs (1)
- # events (7)
- # hoplon (119)
- # instaparse (52)
- # keechma (71)
- # mount (4)
- # off-topic (9)
- # om (4)
- # onyx (3)
- # other-languages (23)
- # protorepl (3)
- # re-frame (9)
- # reagent (26)
- # rethinkdb (5)
- # spacemacs (2)
- # testing (1)
- # yada (1)
@drewverlee: See http://www.onyxplatform.org/docs/user-guide/latest/aggregation-state-management.html
Also see the papers listed at the bottom of this blog post http://www.onyxplatform.org/jekyll/update/2015/11/12/Onyx-0.8.0-Automatic-State-Management.html
We use an implementation of WID to store the window contents in memory (https://github.com/onyx-platform/onyx/blob/0.9.x/src/onyx/windowing/window_id.clj#L3) and replicate them onto disk using the techniques described above. The whole window contents need to fit in memory. We'll be implementing an alternate, pluggable windowing technique that pessimistically spills the entire window to disk.