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

Re: [PATCH] Re: log/blame -g and old servers

From: Karl Fogel <kfogel_at_red-bean.com>
Date: 2007-10-22 02:32:40 CEST

Stefan Küng <tortoisesvn@gmail.com> writes:
> May I suggest adding a new API which only detects whether the server
> supports a certain feature?

I think this is what the new capabilities-discovery API added in
r27168 does.

> Something like:
> enum supportedfeature
> {
> mergetracking, // supports merge tracking
> loglimit // supports the --limit switch for logs
> }
>
> enum supportstate
> {
> notsupported, // feature is not supported
> partlysupported,// feature is not supported by server, but client
> has workaround
> fullysupported // server supports the feature completely
> }
>
> supportstate svn_client_check_server_capability(supportedfeature feature);
>
> Then clients could ask the server what it is capable of and then
> decide whether they want to offer a certain feature to the user or
> not.

The current API only says boolean "yes" or "no" that the server
supports the feature, but I'm not sure what the point of the third
state would be. After all, if the client has a workaround, it knows
that, and can decide whether or not to use it. IOW, that's not a
question the server can answer; it's a question the client decides
after querying the server. So the 'partlysupported' state is
equivalent to 'not supported', for the client's purposes.

-Karl

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Oct 22 02:32:50 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.