Re: Fixing depth-handling in the RA interface.

On Wed, Mar 21, 2007 at 11:37:54PM -0700, Karl Fogel wrote:
> expecting depth is easy and "obvious"... but on the client side, it
> seems odd to me that new 1.5 APIs would take a recurse parameter
> instead of depth, even if they're only taking it in order to transmit
> something required for compatibility.
>

It's odd, but I can't think of anything better. Document that the
recurse parameter is used to define recurse/non-recurse behaviour for
servers that ignore the depth parameter on the set_path/link_path calls,
and let the client sort it out. (We're still expecting the client to be
able to ignore extra paths from those servers, right? Or are we
planning to put a filter in place in the RA layer?).

Regards,
Malcolm