This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2024-02-23
Channels
- # announcements (18)
- # beginners (26)
- # calva (12)
- # cider (43)
- # cljdoc (4)
- # clojure (38)
- # clojure-europe (11)
- # clojure-nl (1)
- # clojure-norway (12)
- # clojure-sweden (2)
- # clojure-uk (4)
- # cursive (17)
- # data-science (4)
- # datalevin (2)
- # datomic (3)
- # emacs (10)
- # ghostwheel (4)
- # graphql (11)
- # honeysql (1)
- # hyperfiddle (7)
- # introduce-yourself (1)
- # malli (23)
- # nrepl (11)
- # overtone (1)
- # pathom (9)
- # pedestal (2)
- # polylith (1)
- # portal (3)
- # reitit (1)
- # shadow-cljs (12)
- # timbre (4)
- # vim (2)
- # xtdb (4)
Is it normal (expected) that I can freely mix and match Sieppari sync and async interceptors? In the context of a legacy app, I'd be interested in keeping using a traditional Jetty (threaded) sever, and a sync http client within backend code. Interceptors would be an awesome fit as, I think, it would allow to not block Jetty on IO, while not introducing too much risk (in form of async http clients, Loom threads, etc) https://github.com/metosin/reitit/blob/ca434f9c05049c01a47066c1fb57e1b59e693b1b/examples/http/src/example/server.clj looks promising enough - I reckon that interceptor chain can mix sync and async. Any specific insight welcome