You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
HttpServerRequest does not provide a way to get a handle to netty's ChannelHandlerContext as HttpServerResponse does.
This makes it awkard for code which wants an access to Channel details and is only interested in the request to either pass the ChannelHandlerContext directly or HttpServerResponse.
The text was updated successfully, but these errors were encountered:
…IngressRequest.
When RxNetty provides a way to get ChannelHandlerContext from HttpServerRequest (Issue 214: ReactiveX/RxNetty#214) we will only need this in EgressRequest.
NiteshKant
changed the title
HttpServerRequest should provide a way to access ChannelHandlerContext
HttpServerRequest should provide a way to access Netty channel
Sep 7, 2014
Returning a ChannelHandlerContext is ambiguous as it is unclear which ChannelHandler does this context belong to. So, instead it should return the Channel
HttpServerRequest
does not provide a way to get a handle to netty'sChannelHandlerContext
asHttpServerResponse
does.This makes it awkard for code which wants an access to
Channel
details and is only interested in the request to either pass theChannelHandlerContext
directly orHttpServerResponse
.The text was updated successfully, but these errors were encountered: