Re: [Duplicity-talk] slowness+ ftp timeouts with 0.4.3-rc1

[dAniel hAhler]

IMHO sending NOOP (or better randomly NOOP, PWD or SYST - to let the
server not detect the keep alives), is not worth the trouble: we would
probably need a thread for this or implement something to simulate
threading.
It's no problem to re-login: with the latest backends.py file I've
sent there is no delay on the first caught exception. So the whole
"overhead" would be just to re-login (and maybe also re-connect) in
this case.

On 5/31/07, Charles Knowlton <address@hidden> wrote:
> I don't know much about programming but I know my ftp client has an
> option to send keep alives.
> I don't know the behind the scenes working of this.  It could very
> well be using NOOP but I have no clue.
> The ftp software I use is YummyFTP.  The website is http://
> www.yummysoftware.com/
> Hope this helps.
>
> Charles
>
> On May 31, 2007, at 1:29 PM, Kenneth Loafman wrote:
>
> > Charles Knowlton wrote:
> >> Couldn't you just send a keep alive to the ftp server to keep the
> >> connection active?
> >> I assume that most ftp servers support this feature.
> >
> > That's what the NOOP is intended to do, but if keep_alive is a
> > better option I'll use it instead.  I've never used it.
> >
> > ...Ken
> >
> >
> > _______________________________________________
> > Duplicity-talk mailing list
> > address@hidden
> > http://lists.nongnu.org/mailman/listinfo/duplicity-talk
>
>
>
> _______________________________________________
> Duplicity-talk mailing list
> address@hidden
> http://lists.nongnu.org/mailman/listinfo/duplicity-talk