dAniel hAhler wrote:
Hello,
I've provided/extended a patch [1] for the FTP backend of duplicity,
which retries a failed command in case of an exception.
This is very useful and in fact required with some backup servers.
Unfortunately this only provides this functionality for the FTP
backend.
Thanks for the patches. I'm working on them now, along with a
patch to ftplib.py that is not complete. Python's ftplib.py breaks
with ProFTPD with or without the patch. Error handling in FTP is
messy.
Now, that there's already a similar patch for SCP [2], I think it
should get refactored and become a feature/implementation of the
Backend base class itself, so all backends make use of it and there
can be some global config settings for it.
>
Additionally, it's a lot more maintainable to have this type of
functionality in the parent class than in each child, by applying the
different patches/attempts.
What do you think?
What's planned?
Actually, there's similar functionality, via patches, for most, if
not all of the backends, all slightly different, and all having
different needs w.r.t. determining exactly what an error is for its
protocol. Refactoring into the Backend class will come in one of
the next releases. Its truly a sticky problem.
and btw: where does the duplicity source get hosted? Will the project
stay at savannah.nongnu.org? Can we switch to Subversion (instead of
CVS)?
It's still at Savannah. I see no reason to change, but I would
like to move to Subversion ASAP.
I'm happy that there's finally a maintainer again!
Thanks a lot.
[1] http://savannah.nongnu.org/patch/?5183
[2] http://savannah.nongnu.org/patch/?5794
These will be implemented in the next version, 0.4.3.
Thanks for the help!
...Ken
_______________________________________________
Duplicity-talk mailing list
address@hidden
http://lists.nongnu.org/mailman/listinfo/duplicity-talk