>
> Hi again,
>
> On Mon, Jul 1, 2019 at 3:16 PM Jakub Janku wrote:
> >
> > Hi,
> >
> > On Mon, Jul 1, 2019 at 1:02 PM Frediano Ziglio wrote:
> > >
> > > >
> > > > The current approach with OutputQueue in webdav has several problems:
> > > >
> > > > * if the connection is slow, webdav keeps
Hi again,
On Mon, Jul 1, 2019 at 3:16 PM Jakub Janku wrote:
>
> Hi,
>
> On Mon, Jul 1, 2019 at 1:02 PM Frediano Ziglio wrote:
> >
> > >
> > > The current approach with OutputQueue in webdav has several problems:
> > >
> > > * if the connection is slow, webdav keeps reading from phodav
> > > and
Hi,
On Mon, Jul 1, 2019 at 1:02 PM Frediano Ziglio wrote:
>
> >
> > The current approach with OutputQueue in webdav has several problems:
> >
> > * if the connection is slow, webdav keeps reading from phodav
> > and pushing messages to the internal channel xmit_queue.
> > This way, the queue can
>
> >
> > The current approach with OutputQueue in webdav has several problems:
> >
> > * if the connection is slow, webdav keeps reading from phodav
> > and pushing messages to the internal channel xmit_queue.
> > This way, the queue can grow very quickly and the whole file
> > that is being
>
> The current approach with OutputQueue in webdav has several problems:
>
> * if the connection is slow, webdav keeps reading from phodav
> and pushing messages to the internal channel xmit_queue.
> This way, the queue can grow very quickly and the whole file
> that is being transferred using
The current approach with OutputQueue in webdav has several problems:
* if the connection is slow, webdav keeps reading from phodav
and pushing messages to the internal channel xmit_queue.
This way, the queue can grow very quickly and the whole file
that is being transferred using webdav
