You're right, Nikki,-- he has. There was a point to all this in the
beginning but I think it's all good now.
All seems to work as advertized. I went back to some earlier test cases
and what I thought was failing
is in fact working fine.
-Igor.
On Mon, Sep 23, 2013 at 11:56 PM, Niki Dokovski
On Tue, Sep 24, 2013 at 8:15 AM, Igor Urisman igor.uris...@gmail.comwrote:
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
On 22/09/2013 21:49, Igor Urisman wrote:
However, the server implementation is free to pick the maximum size of a
payload
that it is willing to receive as a whole. Tomcat designers chose that size
to be 125
bytes. Reasonable number given the particulars of the wire level protocol,
but not
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
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.
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?
-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
Mark,
Sorry for the delay in responding. I am working on this project in my spare
time.
That I was missing something wasn't the question. The question was what.
I think I figured it out, but wanted to follow up for two reasons. One is
the benefit of
others in my situation (this stuff is still
On 18/09/2013 06:19, Igor Urisman wrote:
Dear All,
I am looking for help in understanding why the size of the inbound
WebSocket message is limited to 125 bytes.
It isn't, at least not by Tomcat.
I realize that this may not
even be the right place for my question, but am still hoping for
Dear All,
I am looking for help in understanding why the size of the inbound
WebSocket message is limited to 125 bytes. I realize that this may not
even be the right place for my question, but am still hoping for a clue.
From looking at the RFC 6455, Sec. 5.2 Base Framing Protocol, I am making
