filelist caching optimization proposal

Edwin Eefting edwin at
Mon May 23 14:48:03 GMT 2005

On Monday 23 May 2005 16:09, Christoph Biedl wrote:
> > -What are the most likely problems i would run into when i try to
> > implement this?
> You can expect a feature request that allows to manipulate certain parts
> of the cache only (re-scan or delete a subtree). This would turn the
> cache into a database but will surely introduce a lot of trouble to
> implement.
> Other problems like the forseeable synchronisation problems and races in
> the cache generation should be caught by locking and/or "It's a
> feature".

Thanks...I like the 'its a feature method' :)
It shouldn't be much of a problem with locking, and some kind of 
--refresh-cache option.

>     Christoph

  //||\\  Edwin Eefting
 || || || DatuX, Linux solutions and innovations

        Nieuw Amsterdamsestraat 40
        7814 VA Emmen
        Tel. 0591-857037
        Fax. 0591-633001
Dit e-mailbericht is alleen bestemd voor de geadresseerde(n). Gebruik
door anderen is niet toegestaan. Indien u niet de geadresseerde(n) bent
wordt u verzocht de verzender hiervan op de hoogte te stellen en het
bericht te verwijderen. Door de elektronische verzending kunnen aan de
inhoud van dit bericht geen rechten worden ontleend.
The information contained in this e-mail is intended only for the
individual(s) to whom it is addressed. Using contents of this email by
others than the intended recipient(s) is strictly prohibited. If you are
not the intended recipient(s), please notify the sender immediately, and
delete this email. You cannot derive nor conclude any rights from the
contents of this e-mail.

More information about the rsync mailing list