sorry, mail did go to soon...
I do this in the web.xml (directly in the web-app tag)
<context-param>
<param-name>org.apache.tomcat.websocket.textBufferSize</param-name>
<param-value>32768</param-value>
</context-param>
<context-param>
<param-name>org.apache.tomcat.websocket.binaryBufferSize</param-name>
<param-value>32768</param-value>
</context-param>
But this doesn't seem to have any effect, i still see in the browser stuff
like frames of max 8192 (and continuation frames)
We have problems (with chrome) with all kinds of errors when sending these
frames (invalid opcode, utf char encoding problem, reserved words 1 ,2 ,3
errors in the browser)
So i want to see if i just don't use frames what the result is then
Johan
On 16 November 2013 15:09, Johan Compagner <jcompag...@servoy.com> wrote:
> Hi
>
> i read this:
>
> http://tomcat.apache.org/tomcat-7.0-doc/web-socket-howto.html
>
> so what i do is add this into the web.xml
>
> --
> Johan Compagner
> Servoy
>
--
Johan Compagner
Servoy
