This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-08-21
Channels
- # admin-announcements (1)
- # beginners (3)
- # boot (242)
- # clara (1)
- # cljsrn (8)
- # clojars (2)
- # clojure (68)
- # clojure-russia (23)
- # clojure-spec (28)
- # clojure-uk (11)
- # clojurescript (7)
- # datavis (3)
- # datomic (21)
- # emacs (2)
- # events (2)
- # hoplon (56)
- # jobs (3)
- # lambdaisland (1)
- # mount (20)
- # off-topic (4)
- # om (13)
- # onyx (17)
- # other-languages (2)
- # parinfer (7)
- # proto-repl (2)
- # proton (2)
- # protorepl (53)
- # re-frame (13)
- # reagent (3)
- # ring-swagger (22)
- # specter (5)
hi all, what's is the om.next way to push updates from server to client?
eg in a chat app?
@myguidingstar call om.next/merge!
with the novelty
well, I want to know the recommended medium to transfer the novelty, too. For instance, the old way is to put arbitrary data to websocket or polling then add an event listener
that’s just out of scope of Om Next
what matters is how you side-load your data into the app
which is what I answered
whichever method you use (websockets, polling, SSE…) is completely up to you
okay, got it
you're right, om.next/merge! is the sufficient answer. Thanks a lot
@ethangracer I went down that rabbit hole, so voilà: https://github.com/compassus/omify
haven’t had the time to write docs, but you can get the big picture from the devcards examples: https://github.com/compassus/omify/blob/master/src/devcards/omify/devcards/core.cljs
(I also included one using Recharts)