Sorry for the slow response time.
On Tue, 2003-07-15 at 17:11, Tony Hoyle wrote:
> For the client side, is using svn+sspi:// or just sspi:// prerered? (I'd
> guess the svn+... syntax, from looking at the code).
svn+foo:// is for using external agents. If the code is going to be
internal to Subversion, the preferred method is to use the SASL
authentication framework within the regular svn protocol. Of course,
that requires that there be a SASL mechanism defined for the given
security back-end.
> (btw. I would do ssh, for which I have a patched Putty DLL, but you're
> already using that for external protocols :/).
I don't understand the frowny here.
> Is there any code at the moment for gzipping the output and/or
> encrypting it? Certainly the gzip would help as checking out the
> subversion repository was really slow given that it's mostly text files.
The only way to check out the Subversion repository is over HTTP, so why
is that relevant to ra_svn? Also, isn't it a leap to assume that any
slowness is due to network bandwidth? If the slowness is due to CPU
consumption, gzip will only make things worse, and if the slowness is
due to disk bandwidth on the client or server, compression won't matter.
I think checkouts are automatically compressed over ra_svn, because our
editor interface doesn't allow any way to specify file contents except
for deltas. If there's no delta source, a delta against the empty
source still results in some level of compression. (Currently, svndiff
self-compression is not as good as gzip, but there are modifications on
the back burner to remedy that.)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Aug 27 16:20:10 2003