Garrett Rooney <rooneg <at> electricjellyfish.net> writes:
> > Agreed. I'd like to ensure that replay can only be done by authorized
> > users/clients (if that's a hook, so be it). If we allow replay on
> > some big public servers, it'd be a bad thing for those shared
> > resources if everyone can do it. We can do a 'email us if you want to
> > be on the replay list' - this is what most RBLs do for rsync services,
> > etc. Yes, they can also do a checkout; but this feature seems a bit
> > scary without a way to curb its capability. I shudder to think what a
> > 380000-revision replay is going to look like.
>
> If there's going to be such a hook, I'd just ask that it at least take
> into account things like the base directory of the replay, so that
> people can use replay to mirror particular branches, which seems safe,
> but be kept from mirroring entire projects or repositories, which
> would be dangerous.
I don't think it makes any sense for restricting a convenient api but not the
expensive one where the user can use to do essentially the same thing,
such as, what svn::mirror does, reverse engineering the log output and use
the fulltext delta to reconstruct a revision.
I guess a sensible default in the client to DTRT is more a priority than
server-side throttle.
Cheers,
CLK
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Feb 24 13:02:23 2006