This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-10-14
Channels
- # aleph (14)
- # bangalore-clj (2)
- # beginners (39)
- # boot (18)
- # carry (7)
- # cider (37)
- # cljs-dev (1)
- # cljsrn (4)
- # clojure (74)
- # clojure-austin (12)
- # clojure-canada (6)
- # clojure-conj (15)
- # clojure-dev (3)
- # clojure-greece (14)
- # clojure-italy (1)
- # clojure-korea (1)
- # clojure-poland (3)
- # clojure-russia (5)
- # clojure-spec (22)
- # clojure-uk (13)
- # clojurebridge (9)
- # clojurescript (231)
- # cursive (2)
- # datascript (9)
- # datomic (12)
- # devcards (2)
- # emacs (2)
- # events (4)
- # hoplon (28)
- # off-topic (35)
- # om (61)
- # onyx (8)
- # parinfer (8)
- # proton (1)
- # re-frame (53)
- # reagent (10)
- # ring-swagger (8)
- # specter (11)
- # untangled (3)
- # vim (4)
I'm using aleph.udp/socket for sendin messages. When receiving messages that have the payload over 2048 characters (json encoded strings), then the payload is chomped to be 2048 characters. Rest of the payload is just dropped.
Is there a way of telling aleph/udp directly that i'd like to have larger payloads/mtu/whatever is limiting the size of the payload?
i’m pretty sure that aleph allows you to directly pass options to netty when you create servers/sockets
looks like this is not the case. interesting. you probably are going to have to call netty functions directly
@elahti can this be relevant? http://stackoverflow.com/questions/11525712/why-is-netty-giving-me-only-768-bytes-from-udp-messages