> From: sussman@collab.net [mailto:sussman@collab.net]
> Sent: 26 July 2002 00:20
> "Sander Striker" <striker@apache.org> writes:
>
> > > From: sussman@collab.net [mailto:sussman@collab.net]
> > > The INSTALL file, which describes how to build svn client and server,
> > > discuss how to build zlib and ssl into both ends of the network. Do
> > > we need to explain encryption and compression elsewhere, in more
> > > general terms? Perhaps in the "design" section of the Handbook's
> > > chapter 1?
> >
> > The INSTALL file doesn't mention the mod_deflate part IIRC. I can add that
> > later on if noone beats me to it.
>
> Cool.
>
> But I think there's a bigger confusion here.
>
> If you're a CVS user, you're used to thinking about the client always
> being "in control" of communication. That is, you set your
> authentication/encryption by hand: "use pserver", "use ssh", and so
> on.
>
> But SVN is a total reversal on this paradigm, because of HTTP. Now
> the *server* is in control. If you want a certain kind of
> authentication or encryption, then you set up your server exactly that
> way. The client is challenged by the server, and it better know how
> to respond. If the client can't do basic auth, or certificates, or
> speak ssl to an https:// url or whatever... then no dice.
>
> I think this idea should be described in the 'SVN for CVS Users'
> appendix of the Handbook, no?
Agreed. +1.
Sander
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Jul 26 00:36:57 2002