This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2015-09-22
Channels
- # admin-announcements (5)
- # aws (32)
- # beginners (2)
- # boot (51)
- # cider (33)
- # cljs-dev (4)
- # clojure (83)
- # clojure-berlin (11)
- # clojure-czech (23)
- # clojure-poland (3)
- # clojure-russia (51)
- # clojure-seattle (4)
- # clojure-sg (1)
- # clojure-uk (4)
- # clojurescript (48)
- # clojurex (1)
- # datomic (26)
- # devcards (10)
- # devops (12)
- # editors (9)
- # emacs (12)
- # events (1)
- # funcool (14)
- # hoplon (117)
- # immutant (1)
- # jobs (2)
- # ldnclj (32)
- # ldnproclodo (12)
- # om (51)
- # onyx (17)
- # reagent (11)
- # yada (4)
@voytech: it might be possible - it's based around manifold, which interops with core.async channels as well as it's own Deferred values, so it may be feasible to adapt it to another web-server (like http-kit) which does a similar thing to aleph, but with core.async channels instead of Deferreds. @malcolmsparks will have a more authoritative answer
Hi @voytech - @mccraigmccraig is right, it should be possible to support other web-servers. However, I want to get all the planned functionality completed using aleph, including chunked responses (i.e. transfer encodings) so that this functionality isn't made impossible by the need to support it in other web servers
The aim is to get everything working optimally with aleph, and then write adapters to other web servers (http-kit, Jetty, Immutant, etc.)