This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-11-06
Channels
- # beginners (3)
- # boot (2)
- # cljs-dev (11)
- # cljsrn (122)
- # clojars (9)
- # clojure (8)
- # clojure-austin (5)
- # clojure-korea (1)
- # clojure-russia (3)
- # clojure-spec (7)
- # clojure-uk (14)
- # clojurescript (45)
- # cursive (12)
- # emacs (7)
- # euroclojure (1)
- # hoplon (285)
- # instaparse (1)
- # klipse (37)
- # leiningen (1)
- # off-topic (3)
- # om (11)
- # onyx (4)
- # re-frame (5)
- # reagent (1)
- # sql (3)
- # uncomplicate (2)
- # untangled (17)
- # vim (5)
I was thinking you could use co.paralleluniverse.pulsar.dataflow/df-val
(see https://github.com/puniverse/pulsar/blob/master/docs/index.md#dataflow-reactive-programming) as a replacement for reagent's reaction
and then use re-frame on the server mostly as is: i.e. have event handlers that transition your app-db/state and have subscriptions/a signal graph with query logic listening to app-db changes and propagate those changes to the outside world (not the view layer in this case but a websocket connection or a message queue).
@andreas-thoelke nice idea, I am on the same page, in a app of mine I basically do the same with core.async but I have read so many good things about pulsar (instrumentation finally 👍), need to try it out sooner or later
is https://github.com/ptaoussanis/sente the way to go if you want to use websockets in re-frame or is there alternatives ?
@decoursin re-frame runs in CLJ and CLJS, though CLJ is mostly for testing
Theoretically if you could run Reagent in Clojure, you could pair it with re-frame