In cases, when there is a need to write infinite (or streams with unpredictable lengths) on a connection, the only practical way to flush data is to use flushOnEach as coming to an adequate buffer size/ time boundary is just too hard and error prone.
It would be nice to be able to tell RxNetty to flush all pending writes on the next eventloop iteration. It should still be possible to issue explicit flush() but in absence of an explicit flush, the writes must be flushed with every eventloop iteration.
In cases, when there is a need to write infinite (or streams with unpredictable lengths) on a connection, the only practical way to flush data is to use
flushOnEach
as coming to an adequate buffer size/ time boundary is just too hard and error prone.It would be nice to be able to tell
RxNetty
to flush all pending writes on the next eventloop iteration. It should still be possible to issue explicitflush()
but in absence of an explicit flush, the writes must be flushed with every eventloop iteration.