This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2024-02-29
Channels
- # announcements (6)
- # babashka (7)
- # beginners (24)
- # calva (2)
- # cider (21)
- # clj-kondo (49)
- # cljdoc (29)
- # clojure (56)
- # clojure-dev (2)
- # clojure-europe (15)
- # clojure-nl (6)
- # clojure-norway (27)
- # clojure-uk (3)
- # clojuredesign-podcast (6)
- # clojurescript (1)
- # conjure (1)
- # core-async (8)
- # cryogen (2)
- # cursive (6)
- # data-science (1)
- # datomic (12)
- # events (1)
- # fulcro (16)
- # graalvm (28)
- # hyperfiddle (2)
- # lambdaisland (4)
- # leiningen (20)
- # observability (1)
- # off-topic (24)
- # pathom (5)
- # pedestal (10)
- # portal (7)
- # practicalli (1)
- # reitit (5)
- # rewrite-clj (20)
- # shadow-cljs (18)
- # vim (8)
- # xtdb (9)
I'm trying to develop an application on electric and xtdb-in-a-box based on https://github.com/hyperfiddle/electric-starter-app. The server needs to serve two clients, a very simple one at the root that needs to load fast over a slow mobile connection and a potentially much larger client at "/admin" which will have good connectivity. I've had a look at electric fiddle, I don't fully understand its routing yet, I'm guessing it behaves similar to a condition on a reactive value, however it seems the clients share the same runtime-code, an approach which wouldn't support my use-case. It seems to me I need to split my code to have two distinct clients that compile separately against common server code and modify server-jetty.clj middleware to add a conventional router to serve these up with two electric-entrypoints and reactors. Are there likely to be any issues with this? Are there any existing examples of such an approach? TIA