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

Re: connection establishment todo, secure transport, sasl temporary alternative

From: Garrett Rooney <rooneg_at_electricjellyfish.net>
Date: 2002-12-03 15:05:19 CET

solo turn wrote:

>when reading connection establishment
>todo(subversion/libsvn_ra_svn/todo), two things were not clear to me:
>1. why would you need a port assignment from iana, if
> you are using http/webdav/deltav,
> isnt there port 80/443 already "defined"?
>2. why there is nothing saying "ssl" as temporary and easy
> to implement alternative to sasl.
>
>

ra_svn is a different repository access layer than ra_dav.

ra_dav works over http/webdav/deltav, ra_svn works over a tcp connection
with a custom protocol greg hudson has devised. thus, ra_svn will
require a new port assignment, and will have to implement some things
that we already get from ra_dav and apache. on the other hand, it is
likely that the whole of ra_svn's code will be smaller (and thus more
auditable for security issues) than ra_dav and mod_dav_svn/apache, and
that will please many people who don't want something as large and
complex as apache for their svn server. it's a tradeoff though. ra_dav
and apache/mod_dav_svn will likely remain more powerful simply because
of the large amount of stuff we can get from apache.

-garrett

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Dec 3 15:06:16 2002

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.