>
> On Tue, Sep 19, 2017 at 08:33:04AM -0400, Frediano Ziglio wrote:
> > >
> > > On Wed, Sep 13, 2017 at 10:15:14AM +0100, Frediano Ziglio wrote:
> > > > Now the push is done automatically when a PipeItem is added
> > > > (cfr commit 5c460de1a3972b7cf2b9b2944d0b500c3affc363
> > > > "worker: push
On Tue, Sep 19, 2017 at 08:33:04AM -0400, Frediano Ziglio wrote:
> >
> > On Wed, Sep 13, 2017 at 10:15:14AM +0100, Frediano Ziglio wrote:
> > > Now the push is done automatically when a PipeItem is added
> > > (cfr commit 5c460de1a3972b7cf2b9b2944d0b500c3affc363
> > > "worker: push data when
>
> On Wed, Sep 13, 2017 at 10:15:14AM +0100, Frediano Ziglio wrote:
> > Now the push is done automatically when a PipeItem is added
> > (cfr commit 5c460de1a3972b7cf2b9b2944d0b500c3affc363
> > "worker: push data when clients can receive them"),
> > forcing a push cause only network fragmentation
On Wed, Sep 13, 2017 at 10:15:14AM +0100, Frediano Ziglio wrote:
> Now the push is done automatically when a PipeItem is added
> (cfr commit 5c460de1a3972b7cf2b9b2944d0b500c3affc363
> "worker: push data when clients can receive them"),
> forcing a push cause only network fragmentation and is
Now the push is done automatically when a PipeItem is added
(cfr commit 5c460de1a3972b7cf2b9b2944d0b500c3affc363
"worker: push data when clients can receive them"),
forcing a push cause only network fragmentation and is required only if
you are handling data in a polling loop (and thus, you are