Re: [Duplicity-team] [Merge] lp:~mterry/duplicity/early-catch-498933 into lp:duplicity

2011-08-24 Thread edso
in this case it means we add a new interface like get_info() that backends are free to implement. if they do, some extra duplicity functionality kicks in. if not, then it does not ;). But no reason to invent some complicated thing that all backends have to support. Why not do

Re: [Duplicity-team] [Merge] lp:~mterry/duplicity/early-catch-498933 into lp:duplicity

2011-08-24 Thread edso
On 24.08.2011 16:12, Michael Terry wrote: I feel like the importance of the details of the API design, while not a trivial matter, has still been dwarfed by the amount of virtual ink we've spilled. :) that's the nice thing of going paperless ;) you might have noticed, i try to model future

Re: [Duplicity-team] [Merge] lp:~mterry/duplicity/early-catch-498933 into lp:duplicity

2011-08-24 Thread edso
On 24.08.2011 16:31, Kenneth Loafman wrote: I think you two have indeed hashed the design down to it's essentials, so here are some thoughts on the issue. The idea of get_info(filename_list) is a good idea, but it is not necessary to specify what info to return. It is necessary for this