This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-04-06
Channels
- # architecture (2)
- # aws (6)
- # bangalore-clj (3)
- # beginners (7)
- # boot (29)
- # cider (26)
- # cljs-dev (52)
- # cljsrn (1)
- # clojure (249)
- # clojure-dev (9)
- # clojure-italy (2)
- # clojure-norway (3)
- # clojure-russia (178)
- # clojure-uk (30)
- # clojureremote (6)
- # clojurescript (91)
- # core-async (4)
- # cursive (8)
- # datascript (3)
- # datavis (1)
- # datomic (6)
- # emacs (3)
- # figwheel (2)
- # hoplon (14)
- # incanter (6)
- # luminus (8)
- # mount (7)
- # off-topic (22)
- # om (25)
- # onyx (41)
- # pedestal (7)
- # re-frame (9)
- # ring (1)
- # spacemacs (4)
- # sql (1)
- # uncomplicate (1)
- # unrepl (37)
- # untangled (90)
- # yada (77)
@lucian303 What is wrapping the GET?
@curlyfry it's in a context
inside a defroutes
... apparantely that should have been a defapi
, it seems. thanks for your help. i didn't realize it until i went back to look more closely at the code
@lucian303 :thumbsup: No problem
Anyone know of a good example using luminus and jetty for server sent events? Not sure If I should follow the ring docs and return a three arg handler or the qubits/jet docs and return an async channel … neither seem to work for me and I’m not sure what I’m doing wrong. Thanks in advance.
@juliobarros haven't played with jet in a while, one thing to check might be the middleware you have around the route
you could try with immutant as well unless jetty is a requirement http://immutant.org/documentation/2.0.0-beta2/apidoc/immutant.web.sse.html
Thanks @yogthos Jetty is a semi-requirement since client is used to it and managing self signed certs in their env. My thought was the middleware … but I haven’t gotten it to work yet even by stripping things out … will have to sleep on it. Thanks again.