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

Re: Re: svn commit: r23760 - in branches/sparse-directories/subversion: libsvn_ra_svn svnserve

From: Peter Lundblad <plundblad_at_google.com>
Date: 2007-03-12 10:34:29 CET

Greg Hudson writes:
> I'm with Peter on this one. I don't see why we should be
> second-guessing the future necessity of depth in particular as a
> parameter, nor do I think that parameters in general should be made
> optional just because they might some day in some unknown way become
> obsolete. (I realize in this case it's zero-cost to do so because
> backward-compatibility already forces the server to handle the case of
> an unspecified depth. But it's conceptually messy, to me, and it's a
> bad precedent.)

Yeah, my intention was to make the protocol easy to understand.
If you make a parameter optional, you must document its meaning *today*
(which was depth infinitiy) and then clients start relying on that...


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Mar 12 10:35:04 2007

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.