[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: svn commit: r29773 - branches/in-memory-cache

From: Blair Zajac <blair_at_orcaware.com>
Date: Fri, 07 Mar 2008 15:48:09 -0800

glasser_at_tigris.org wrote:
> Author: glasser
> Date: Fri Mar 7 10:23:54 2008
> New Revision: 29773
> Log:
> On the in-memory-cache branch:
> * README.branch
> Add a README, including a basic outline of the API I'm going to add
> and the implementation it's going to use.
> Added:
> branches/in-memory-cache/README.branch
> Added: branches/in-memory-cache/README.branch
> URL: http://svn.collab.net/viewvc/svn/branches/in-memory-cache/README.branch?pathrev=29773
> ==============================================================================
> --- (empty file)
> +++ branches/in-memory-cache/README.branch Fri Mar 7 10:23:54 2008
> @@ -0,0 +1,102 @@
> +This branch adds a simple in-memory cache library that handles
> +annoying memory-management details for you. FSFS has several
> +hand-written caches already; this will reduce duplicate code and make
> +it easier to add more.
> +
> +NULL is a legitimate value. There is no cache_delete (but you can set
> +to NULL, which may be good enough).

It seems that any cache would want a cache_delete method. I've written a server
that exposes svn via Ice and it would be handy to have a cache.

What about adding some fields in the structures to make an LRU cache possible
such as adding to the cache_entry the last time it was looked up. I guess one
could also wrap the value in another value that has those fields, so leaving
this alone would be good.

But I think you'll always want a way of removing entries.


To unsubscribe, e-mail: dev-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: dev-help_at_subversion.tigris.org
Received on 2008-03-08 00:48:22 CET

This is an archived mail posted to the Subversion Dev mailing list.