Re: Request: make the user agent string a define

SteveKing wrote:
> So, you discover that a client has a bug and the server doesn't reject
> the commit. Now what do you do? The only thing you can do is wait for a
> new release of the server, but that will take some time because such a
> bug is not urgent enough (after all, it's the client who sends garbage
> data). During the time in which you wait for a new server release, you
> can then only pray that all your users don't use that broken client
> anymore - not a very good scenario if you ask me.

Or, you can implement appropriate checking in the pre-commit script.

But, more to the point, why are we discussing methods to solve a problem
which has already been solved?

> But let's kick aside the why and what for that feature is needed and
> what would be different and in your opinion much better solutions.
> Let's just accept that users want such a feature, even if you don't
> understand why they want it.

We are having a philosophical disconnect here.

First, if we don't understand why a feature is wanted, how can we do a good
job of designing it?

Second, when better solutions have been raised for every use case so far
mentioned, why would we want to implement the feature?

> So would it be possible to make that user-agent string so that a client
> can change it? I'd really hate it if I had to patch Subversion too - I
> already had to do it with apr-iconv...

So would I.

But would you even *want* to, when we've provided better ways to handle the
problems you've cited as reasons for wanting the feature?

Max.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Jan 8 23:17:16 2005