This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2021-04-16
Channels
- # announcements (1)
- # aws (6)
- # babashka (17)
- # beginners (30)
- # calva (12)
- # cider (25)
- # circleci (2)
- # clojure (42)
- # clojure-australia (8)
- # clojure-czech (1)
- # clojure-europe (30)
- # clojure-france (52)
- # clojure-italy (2)
- # clojure-nl (16)
- # clojure-serbia (3)
- # clojure-uk (10)
- # clojurescript (40)
- # core-async (5)
- # cursive (24)
- # datalog (7)
- # datomic (8)
- # emacs (4)
- # events (1)
- # figwheel-main (3)
- # fulcro (2)
- # helix (5)
- # heroku (1)
- # kaocha (6)
- # leiningen (3)
- # malli (11)
- # music (5)
- # off-topic (20)
- # practicalli (1)
- # re-frame (4)
- # react (8)
- # reitit (14)
- # rewrite-clj (5)
- # rum (2)
- # schema (2)
- # shadow-cljs (23)
- # vrac (28)
- # wasm (4)
- # xtdb (12)
- # yada (5)
I think it's perfectly OK to use whatever middleware including Reitit middleware that makes sense in your application. What I'm arguing for is that you should use the same set of middleware if you want to achieve the 'uniform interface' constraint of REST. The set of middleware I'm proposing in the talk and rest.guide is designed to be used together, in a particular order, to achieve conformance. I'll try to specify the 'rules' for each step so it's clear what the semantics are of each step. That will make it easier to replace parts of the chain with other middleware.
Gotcha. Makes sense. Thanks, Malcolm!