Netty message framing for data frames

Question

I am implementing a very simple websocket server using Netty (v4). I am basing my code on the websocket example source code that comes with Netty. Do I need to do anything extra to handle framing/fragmentation/packet boundaries? Or can I assume that the example code reassembles the data correctly?

The example uses calls like:

String request = ((TextWebSocketFrame) frame).text();

or:

ctx.channel().write(new TextWebSocketFrame(request.toUpperCase()));

So it doesn't seem to be dealing with fragmentation (at that layer at least). Many Thanks.

score 0 · Answer 1 · answered Oct 02 '13 at 04:43

0

The frames are handled as complete frames. If you need to aggregate also ContinumWebSocketFrames you can put WebSocketFrameAggregator in the ChannelPipeline.

answered Oct 02 '13 at 04:43

Norman Maurer

23,104
2
33
31

Does the WebSocketFrameAggregator also aggregate outgoing frames? I know the HttpObjectAggregator does, but can't for the life of me work out how! – Jeremy Field Apr 25 '21 at 14:55
Both only aggregate inbound frames. – Norman Maurer Apr 25 '21 at 18:22
Aaaaaah I finally get it. HttpObjectAggregator only affects requests on server and responses on client! Thanks so much for reply. – Jeremy Field Apr 25 '21 at 21:41

Netty message framing for data frames

1 Answers1