This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-05-22
Channels
- # aws (5)
- # bangalore-clj (3)
- # beginners (84)
- # boot (31)
- # carry (1)
- # cider (6)
- # cljsrn (7)
- # clojure (188)
- # clojure-conj (1)
- # clojure-dev (3)
- # clojure-dusseldorf (8)
- # clojure-greece (10)
- # clojure-italy (7)
- # clojure-nl (3)
- # clojure-russia (45)
- # clojure-spec (5)
- # clojure-uk (64)
- # clojurescript (83)
- # clr (9)
- # core-async (45)
- # cursive (55)
- # datomic (8)
- # devops (1)
- # emacs (7)
- # graphql (1)
- # hoplon (3)
- # jobs (1)
- # jobs-discuss (37)
- # lein-figwheel (3)
- # leiningen (4)
- # luminus (6)
- # off-topic (5)
- # om (2)
- # onyx (33)
- # pedestal (13)
- # re-frame (9)
- # reagent (28)
- # rum (15)
- # specter (4)
- # unrepl (38)
- # vim (3)
@jfntn I think I remember reading that you shouldn't use io.pedestal.interceptor.chain/terminate
but instead just add a :response to the context.
@jfntn @julianwegkamp When using Pedestal to build web services, you can either use terminate
or attach a response. That’s because the servlet-interceptor
always attaches a terminator function that looks for the response.
But if you remove or replace that terminator function with your own custom function, you can still use terminate
.
Or, if you use interceptors for something other that web services, you can use terminate
or define your own terminator functions. (I’ve got a library where I use Pedestal interceptors for Kafka messages… there’s no natural terminator function there so I use terminate
when needed.)
thx @mtnygard. Is this the Kafka library Paul mentioned in his talk and will it become publicly available?
I just don’t have any particular schedule for releasing it. It’s very raw at the moment and I don’t want to get people’s expectations up too much.
Thx. Just looking at your code will be interesting enough I assume. Will try to make some time in the coming week...