a270a4b84c
Motivation: At the moment we only expose close(...) methods that take a Channel as paramater. This can be problematic as the write will start at the end of the pipeline which may contain ChannelOutboundHandler implementations that not expect WebSocketFrame objects. We should better also support to pass in a ChannelHandlerContext as starting point for the write which ensures that the WebSocketFrame objects will be handled correctly from this position of the pipeline. Modifications: - Add new close(...) methods that take a ChannelHandlerContext - Add javadoc sentence to point users to the new methods. Result: Be able to "start" the close at the right position in the pipeline. |
||
|---|---|---|
| .. | ||
| src/main | ||
| .gitignore | ||
| pom.xml | ||