Hi
I have just tested it more, now just with the examples tomcat ships (the
chat example)
What i first did is add in web.xml these lines:
<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>
(right after metadata-complete="true"> so right at the beginning of the
web-app tag)
then i changed the ChatAnnotation class, in the incoming method i added 3
lines of code:
filteredMessage =
filteredMessage+filteredMessage+filteredMessage+filteredMessage+filteredMessage+filteredMessage+filteredMessage;
filteredMessage =
filteredMessage+filteredMessage+filteredMessage+filteredMessage+filteredMessage+filteredMessage+filteredMessage;
filteredMessage =
filteredMessage+filteredMessage+filteredMessage+filteredMessage+filteredMessage+filteredMessage+filteredMessage;
so that the message send back will be large
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? I expect that i can send now 32K at
once of text (or binary) withing that "continuation frame"
Johan
On 19 November 2013 09:38, Johan Compagner <[email protected]> wrote:
>
>
>
> On 19 November 2013 03:55, Igor Urisman <[email protected]> wrote:
>
>> Upgraded my environment to 8RC5 and this feature works for me.
>> Don't know how much help this is, but here's my deployment descriptor:
>>
>> <?xml version="1.0" encoding="UTF-8"?>
>>
>> <web-app xmlns="http://java.sun.com/xml/ns/javaee";
>> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
>> xsi:schemaLocation="http://java.sun.com/xml/ns/javaee
>> http://java.sun.com/xml/ns/javaee/web-app_3_0.xsd";
>> version="3.0">
>>
>> <display-name>FERMI Framework Test Application</display-name>
>>
>> <context-param>
>> <param-name>org.apache.tomcat.websocket.textBufferSize</param-name>
>> <param-value>10240</param-value>
>> </context-param>
>>
>> </web-app>
>>
>>
> So if you do that, and you send large stuff to the browser then for
> example in Chrome in the network tab
> you do see on the websocket connection that the frames are bigger then 8K
> ? So in your example the frames are break up in 10k?
>
>
> johan
>
--
Johan Compagner
Servoy
