On Tue, Sep 24, 2013 at 8:15 AM, Igor Urisman <igor.uris...@gmail.com>wrote:
> Thanks again, Mark, for the quick turnaround. > Which of the 5 parameters on this page would be responsible for changing > the 125-byte max whole text message size? > Mark did a great job describing the properties and if it's still unclear looking at the origins is always an option. 125 sizing is for the control frames [1]. The internal buffers for text and binary frames are 8k. Respective sizes are subject to configuration by org.apache.tomcat.websocket.textBufferSize and org.apache.tomcat.websocket.binaryBufferSize Cheers Niki [1] http://tools.ietf.org/html/rfc6455#section-5.5 -Igor. > > > On Mon, Sep 23, 2013 at 9:07 AM, Mark Thomas <ma...@apache.org> wrote: > > > On 23/09/2013 08:44, Igor Urisman wrote: > > > Thanks for the speedy reply, Mark. > > > > > > I have thought about that code for a minute. You're right; what it does > > is > > > construct the entire > > > message in memory. My use case has no use for partials and the message > > > sizes are > > > tens to hundreds of Kb. Didn't mean to defeat anything there, just the > > use > > > case. > > > > > > If there is a way to change the default min size of a whole message, > that > > > would certainly be > > > the way to go,---another right for you. There's only one problem: I > > don't > > > know how. > > > Do you? > > > > See the Tomcat 8 WebSocket docs for details: > > http://tomcat.apache.org/tomcat-8.0-doc/web-socket-howto.html > > > > Mark > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > > For additional commands, e-mail: users-h...@tomcat.apache.org > > > > >
