This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-04-28
Channels
- # aleph (3)
- # babashka (66)
- # beginners (96)
- # calva (45)
- # clj-kondo (28)
- # clojure (30)
- # clojure-dev (2)
- # clojure-europe (20)
- # clojure-germany (22)
- # clojure-norway (4)
- # clojurescript (176)
- # clojutre (1)
- # cursive (23)
- # datalog (6)
- # datomic (7)
- # docker (3)
- # emacs (3)
- # exercism (4)
- # figwheel-main (5)
- # fulcro (8)
- # gratitude (9)
- # hyperfiddle (8)
- # introduce-yourself (2)
- # jobs (2)
- # malli (4)
- # membrane (3)
- # off-topic (17)
- # polylith (3)
- # portal (2)
- # re-frame (27)
- # reitit (3)
- # releases (1)
- # remote-jobs (1)
- # shadow-cljs (152)
- # spacemacs (8)
- # tools-deps (15)
- # vscode (1)
- # xtdb (24)
@lkorogodski Not exactly. When starting the server, you could pass in :raw-stream? true
, which will prevent Aleph from turning the netty ByteBuf objects into an InputStream, but instead, you’ll get a Manifold stream of ByteBufs.
If you want to aggregate the whole request body into a byte[], you probably want to use something like clj-commons.byte-streams/to-byte-array
. The byte-streams library was built to work with the underlying streams of Aleph. Also, check out the examples/
subdirectory to see uses of byte-streams
in action.
Ok, thanks. I just wanted to spare myself some pain with the middleware that reads the response body. Came across a malli
bug when validating the payload.
Post-validation, the body became nil
.