This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-01-17
Channels
- # aws (2)
- # beginners (34)
- # boot (39)
- # cider (28)
- # cljs-dev (2)
- # cljsrn (30)
- # clojure (195)
- # clojure-austin (6)
- # clojure-dev (6)
- # clojure-dusseldorf (1)
- # clojure-france (1)
- # clojure-russia (139)
- # clojure-spec (25)
- # clojure-uk (66)
- # clojurescript (125)
- # community-development (1)
- # core-async (42)
- # cryogen (1)
- # cursive (22)
- # datascript (6)
- # datomic (67)
- # docker (1)
- # emacs (7)
- # events (1)
- # garden (3)
- # hoplon (15)
- # jobs (3)
- # lein-figwheel (10)
- # leiningen (3)
- # luminus (4)
- # mount (2)
- # nginx (1)
- # off-topic (101)
- # om (42)
- # om-next (6)
- # onyx (7)
- # proton (1)
- # protorepl (4)
- # re-frame (15)
- # reagent (30)
- # remote-jobs (1)
- # ring (8)
- # ring-swagger (17)
- # rum (1)
- # spacemacs (2)
- # sql (1)
- # yada (50)
Has anyone attempted to make a “live” dashboard with om-next (ie. a dashboard that continuously get updates on queries)? Is there a way to “unsubscribe” to a query stream once you don’t need the results anymore?
currently we have a REST API where for each endpoint you can add a parameter ?stream=true that will hold the connection open and send updates coming off the datomic tx queue
is anyone aware of a non-trivial om-next application/example with stuff like authorization?
also interested in the backend implementation: how are queries parsed, validated? what about transactions authorization/validation?
just wanted to share something i built with om.next. mainly i chose om/next to learn it + react + clojurescript, but i found it a pleasure to work with. for those building chrome extensions, i also highly recommend chromex. there is some lightweight usage of :remotes in order to asynchronously communicate between chrome extension pages. comments good or bad are welcome. https://github.com/atdixon/SuperSelect