thanks for the fast reply... i guess what i meant was tcp/ip compression in
the sense that cvs uses it. (basically the -z # option). it sounds like
svn will be just as capable.
another question, are you still planning on implementing the security
features outlined in the design doc?
thanks again.
-Isaac
Authorization
By authorization, we mean answering the question:
"Is user X allowed to perform action Y on data Z?"
The Subversion filesystem provides a single interface for answering this
question.
----- Original Message -----
From: "Karl Fogel" <kfogel@newton.ch.collab.net>
To: "Ben Collins-Sussman" <sussman@collab.net>
Cc: "pivotgrind" <pivotgrind@hotmail.com>; <dev@subversion.tigris.org>
Sent: Wednesday, June 26, 2002 1:44 PM
Subject: Re: tcp/ip compression
> Ben Collins-Sussman <sussman@collab.net> writes:
> > > is there any plan to include tcp/ip compression in subversion?
> > > (like in cvs)
> > >
> > > looks like a promising project, I am very interested in seeing the
> > > security authorization feature. keep up the good work.
> >
> > Read the Design document... our server is apache. That means we can
> > use mod_deflate over the wire (zlib), and can use all the
> > authentication features that apache already has.
>
> CVS does tcp/ip compression? I know it uses zlib to compress the data
> it sends, but that's different from actual tcp/ip level compression,
> if I'm not mistaken.
>
> I don't think we have any plans to do this, and am not sure what
> advantages it would bring, considering that application-protocol-level
> compression will pretty much take care of our compression needs.
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Jun 26 20:59:44 2002