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

[Locking] Repos reporter and locks

From: Peter N. Lundblad <peter_at_famlundblad.se>
Date: 2005-01-24 23:19:17 CET


I am currently revving the libsvn_repos reporter that gets a report about
WC revisions and sends back a tree delta. For locking, it needs to store
lock tokens and from the client and senc back lock token removes for
defunct locks (for svn up) or just report all locks in the repository (for
svn st).

My main problem is the latter case. I really don't like the idea of using
svn_fs_get_locks for the anchor of the report and pull all the locks of
the repository into the server memory at once. OTOH, using
svn_fs_get_lock_from_path for every single path might not be very
efficient either. IN fSFS it will do a stat for each path and it looks
like it will be a lot of work for libsvn_fs_bvase too.

The ideal solution would be a depth 1 option to svn_fs_get_locks, but is
the BDB way of storing locks good for this?

Anny comments on this? sussman?


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Jan 24 23:20:07 2005

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.