This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-01-06
Channels
- # announcements (4)
- # aws (2)
- # beginners (48)
- # calva (39)
- # cljsrn (12)
- # clojure (98)
- # clojure-dusseldorf (1)
- # clojure-serbia (2)
- # clojure-spec (13)
- # clojure-uk (13)
- # clojurescript (97)
- # code-reviews (1)
- # datomic (14)
- # fulcro (24)
- # jobs-discuss (160)
- # juxt (1)
- # luminus (2)
- # nrepl (1)
- # off-topic (1)
- # other-languages (1)
- # overtone (1)
- # perun (6)
- # protorepl (16)
- # re-frame (20)
- # reagent (1)
- # reitit (6)
- # rum (8)
- # shadow-cljs (96)
- # spacemacs (8)
- # specter (4)
- # tools-deps (18)
- # uncomplicate (1)
- # vim (1)
Hey, folks. What is(are) the practical difference(s) between using ring vs http with reitit?
@whoneedszzz http has easier async, but basically non-exiting 3rd party interceptor libs. with ring, there are ton’s of existing middleware libs, but async middleware is not that fun to write.
Creating interceptors from existing middleware is kinda trivial thou, here’s an example: https://github.com/metosin/reitit/blob/master/modules/reitit-interceptors/src/reitit/http/interceptors/parameters.clj.
Hmm, ok
Pedestal has a good set of existing interceptors and one can use reitit-http
with it. Goal is to eventually have most of the useful interceptors pre-packaged & integrated with the reitit/sieppari semantics with good docs, so that it would be newbie friendly. Now, just the most useful part pushed out (coercion, exceptions, formatting etc.).
All of this overlap is what's getting me. For what I'm working on currently it really doesn't matter what I use as it's so basic, but I'd like to use something that I would want to use for a larger project and learn it now.