AW: Purging pristines

Hi,

Von: Julian Foad [mailto:julian.foad_at_wandisco.com]

> And IMO we should work on purging unused pristines automatically, for
> 1.7.x if possible.

I agree here that automatic purging of pristines is very useful, although you can do 1.7.0 without it for now (as manual purging is possible).

> I'd like to see purging at a fairly fine-grained level. Does anyone have
> insight about how to do this? What's in my head is that every WC API
> operation that could possibly leave unused pristines should attempt to
> purge unused pristines before returning. The operations that could leave
> unused pristines are basically 'update' and 'switch', although there may
> be some lower level WC API calls that can do so too. The set of pristines
> to be purged could be either all that are currently unused, or just those
> that became unused during the call.

AFAICS, a "commit" operation may also produce unused pristines.

> When I mentioned this before there was some sentiment expressed that the
> delay involved in purging a large set of files could be unacceptably large
> to a GUI client, but I think automatic purging is important and so we have
> to find a way to make it acceptable, whether that involves making it even
> finer grained or adding progress notification for it or something else.

Progress notification is always good. :-)

And maybe it could be made optional (but enabled by default), so clients which perform several operations in a row or are performance critical can delay the purging.

Markus.
Received on 2011-07-28 11:20:48 CEST