This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2021-04-21
Channels
- # announcements (12)
- # aws (1)
- # babashka (82)
- # beginners (89)
- # calva (8)
- # cider (20)
- # clj-kondo (1)
- # clojars (9)
- # clojure (120)
- # clojure-australia (3)
- # clojure-europe (14)
- # clojure-france (24)
- # clojure-germany (3)
- # clojure-italy (16)
- # clojure-nl (1)
- # clojure-spec (3)
- # clojure-uk (22)
- # clojurescript (26)
- # cursive (38)
- # datascript (1)
- # emacs (10)
- # events (1)
- # helix (7)
- # jackdaw (5)
- # jobs-discuss (37)
- # lambdaisland (10)
- # malli (20)
- # meander (2)
- # off-topic (15)
- # pathom (42)
- # quil (1)
- # re-frame (38)
- # react (2)
- # reitit (2)
- # reveal (9)
- # rewrite-clj (3)
- # ring (5)
- # shadow-cljs (84)
- # spacemacs (1)
- # tools-deps (23)
- # vim (8)
- # vscode (1)
What is the current status of ring 2.0 / ring 2.1?
My particular use case is to authenticate a request and use java.nio to serve files out of a zip efficiently, as it stands I need to spawn a thread to run the Files/copy
to copy the file out of the zip to the ring output stream. It’d be nice to be able to just return a java.nio.Path
(in a zip filesystem) to ring and have it automatically copy it via nio (presumably through SeekableByteChannel
) for me.
Reading through the threads at https://github.com/ring-clojure/ring/issues/393 it seems nio support is planned after websocket support and slated for ring 2.1, so likely some years off yet, is that right?!