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

Re: Connection with TSVN to nonApache SVN server

From: Ben Collins-Sussman <sussman_at_collab.net>
Date: 2003-07-07 18:04:58 CEST

Jack Repenning <jrepenning@collab.net> writes:

> At 8:34 AM -0500 7/4/03, Ben Collins-Sussman wrote:
> >The "malformed
> >network data" is what ra_svn/svnserve always says when the protocols
> >don't match.
> So, just askin', but wouldn't
> Server version incompatible with this client version
> be just a teensy bit clearer?
> Bonus points, of course, for
> Server version (0.24.2) incompatible with this client version (0.19.3)
> And of course, I *do* mean "actually put the version into someplace
> recognizable by all product versions, say a header, so the client can
> verify and report this accurately, leaving random other cases of
> actual malformed network data to be reported in the old-fashioned way."

Sure, everybody wants this. But it opens a whole new can of worms.
Now every single ra_svn library needs to keep a list of server
versions it can speak to? And vice versa? This is why most protocols
exchange *features* rather than version numbers (cvs included).

In this particular case, I'm not even sure ghudson needs to implement
either of these things; the easiest thing he could do is version the
protocol itself, and exchange protocol versions. I suppose ghudson
can comment more on this...

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Jul 7 18:06:57 2003

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.