On 25/01/2017 21:12, Preston Price wrote:
> So what is the purpose of a Decoder.TextStream then if not to handle
> incomplete/partial messages?
To interface with other components that wanted to process the data in
that form.
Partial messages feeding an InputStream is doable, but you need to built
So what is the purpose of a Decoder.TextStream then if not to handle
incomplete/partial messages?
Cheers!
On Wed, Jan 25, 2017 at 2:07 PM, Mark Thomas wrote:
> On 25/01/2017 20:53, Preston Price wrote:
> > Is it possible to use a Decoder to handle partial websocket messages?
>
> No. Decoders on
On 25/01/2017 20:53, Preston Price wrote:
> Is it possible to use a Decoder to handle partial websocket messages?
No. Decoders only apply to whole messages.
The closest you will get it is:
- remove the message size limit
- use a partial message handler that buffers up to a limit
- discard data on
Is it possible to use a Decoder to handle partial websocket messages?
On Wed, Jan 25, 2017 at 1:29 PM, Mark Thomas wrote:
> On 25/01/2017 20:25, Preston Price wrote:
> > My environment:
> > java: 1.8.0_102,
> > tomcat: 8.0.39,
> > os:Ubuntu 4.4.0-45-generic,
> > websocket api: 1.1
> >
> > Curren
On 25/01/2017 20:25, Preston Price wrote:
> My environment:
> java: 1.8.0_102,
> tomcat: 8.0.39,
> os:Ubuntu 4.4.0-45-generic,
> websocket api: 1.1
>
> Currently in my application clients will (rarely) send a message that
> exceeds the default (8192 byte) limit for messages. This results in the
>
My environment:
java: 1.8.0_102,
tomcat: 8.0.39,
os:Ubuntu 4.4.0-45-generic,
websocket api: 1.1
Currently in my application clients will (rarely) send a message that
exceeds the default (8192 byte) limit for messages. This results in the
socket being closed by the server with a 1009 code (too big)
