On 19/11/2013 14:15, Johan Compagner wrote: > If i run that (http://localhost:8080/examples/websocket/chat.xhtml) > > Type in a string that will go over the 8K boundary > Then in chrome it will still display a frame of 8K and then "continuation > frame (Opcode 0)" which is the rest. > > am i expecting the wrong thing here?
Yes. > I expect that i can send now 32K at > once of text (or binary) withing that "continuation frame" The buffer sizes control the input buffer - i.e. they control the maximum size of a message that can be received if an application doesn't support partial messages. The output buffers are all 8K. The splitting of a WebSocket message into multiple frames should be transparent to the application. Mark --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
