This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-08-09
Channels
- # beginners (91)
- # boot (5)
- # cider (30)
- # clara (16)
- # cljsjs (3)
- # cljsrn (6)
- # clojure (84)
- # clojure-dev (4)
- # clojure-dusseldorf (1)
- # clojure-italy (15)
- # clojure-nl (2)
- # clojure-spec (5)
- # clojure-uk (120)
- # clojurescript (54)
- # core-async (25)
- # core-matrix (1)
- # css (2)
- # cursive (20)
- # datomic (28)
- # editors (11)
- # emacs (6)
- # figwheel (4)
- # figwheel-main (28)
- # fulcro (36)
- # graphql (7)
- # hyperfiddle (2)
- # jobs (6)
- # jobs-discuss (10)
- # lambdaisland (1)
- # lumo (3)
- # nrepl (20)
- # off-topic (24)
- # pedestal (2)
- # protorepl (3)
- # reagent (3)
- # reitit (2)
- # remote-jobs (1)
- # ring-swagger (26)
- # rum (1)
- # shadow-cljs (247)
- # spacemacs (29)
- # tools-deps (12)
- # vim (15)
for my project i need to build a device that can be installed on-site (at carwashes) and it can control mechanical equipment, i’m using a raspberry pi with nodejs. i wanted to take advantage of all the fulcro websocket features (single queue, acknowledgements, mutations, app-state etc.) how should i go about this?
i was thinking i implement the FulcroApplication
protocol to make a headless nodejs client
except without components or UI
but none of the clj code will work on it
but how will that give the request queue?
so would i still use https://github.com/fulcrologic/fulcro/blob/develop/src/main/fulcro/websockets.cljs?
then i could call the functions defined in FulcroNetwork
protocol
and I got the feeling you wanted to send machines messages from you back-end??? Or directly from the client UI?
if you’re sending from client UI, then there is nothing to do but add it as a remote, but I thin kthat a bad idea, since you don’t want mulitple UIs possibly controlling one bit of hardware without coordination
@currentoor you may like to use Pathom there, with connect you can build a full parser (with async support) that handles queries and mutations
seems like it would be more of a client than a server
and since i’d be using a normal app state, i could just just the default parser no?
yeah, I think I got it wrong, I though you were talking more about communication layer, but you want to do some kind of rendering, right?
@tony.kay all messages to the device will come from the server not UIs
yeah, so everything is inverted…none of Fulcro’s code for networking is built to work in that direction
so yes, you would use that class you pointed at on the client, and then do server pushes to it
Seems to be working
Able to connect to the server