Re: lock scalability

Ben Collins-Sussman wrote:

> Given that svn_repos_fs_(un)lock() will probably -- eventually -- be
> receiving a whole list of locks from the network, cmpilato and I are
> wondering if it makes sense to define the post-(un)lock hooks as taking
> a list of paths *right now*, rather than one path. If somebody decides
> to lock 5000 things at once, it's important to get one email, not 5000
> of them.

Make sure to pass the list via STDIN or something, rather than ARGV, you
don't want to hit arbitrary limits on the number of arguments that can
be passed to a program.

-garrett

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Mar 14 22:41:13 2005