This version (2017/05/27 13:44) is a draft.
Approvals: 0/1

[00:22:16] * ChanServ sets mode: +o temporalfox [00:32:00] * ChanServ sets mode: +o temporalfox

[08:24:35] * ChanServ sets mode: +o temporalfox [09:46:36] * ChanServ sets mode: +o temporalfox

[13:59:29] * ChanServ sets mode: +o purplefox [15:09:54] * ChanServ sets mode: +o temporalfox

[20:13:23] <pikajude> hey, I'm having a weird issue where in one of my route handlers, I set an endHandler on the incoming HttpServerRequest, but if I move all the code into executeBlocking I start getting an IllegalStateException that the request has been read already

[20:14:15] <pikajude> and this is the only handler I have on the route

[20:14:52] <pikajude> i can paste code but it'll take awhile to produce an easily reproducible test case, so I'm just checking whether there are any caveats about reading requests in a separate thread

[20:17:12] * ChanServ sets mode: +o temporalfox [20:17:57] <pikajude> ok, from browsing github it looks like i have to read the body myself on the main thread or netty will discard it [20:17:58] <pikajude> that's weird [20:19:15] <pikajude> doesn't BodyHandler read the entire body into memory? [20:25:42] * ChanServ sets mode: +o temporal_

[21:00:35] * ChanServ sets mode: +o temporalfox [21:52:28] * ChanServ sets mode: +o temporalfox

[22:15:24] * ChanServ sets mode: +o temporalfox [22:38:53] * ChanServ sets mode: +o temporalfox