You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@subversion.apache.org by Marc Strapetz <ma...@smartcvs.com> on 2004/07/05 12:46:04 UTC
Future of svnserve
Hi,
we are currently evaluating possibilities for building a java-based SVN
client, still unsure if to use javahl or not. After reading the SVN book, I
got some uneasy fealing about the future of svnserve, which could be one
starting point for developing a pure java client library. Is the
Apache/WebDAV combination the favoured server component and svnserve just
some attachment for those who don't want to administer Apache? Would it be
appreciated to push svnserve (at least for the first step) by such a client
library or is it counterproductive regarding the future plans of SVN? And
how important is or should be the role of SVN as WebDAV backend?
Thanks in advance for any ideas on this topic.
Best regard,
Marc Strapetz.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: Future of svnserve
Posted by Garrett Rooney <ro...@gmail.com>.
On Mon, 5 Jul 2004 14:46:04 +0200, Marc Strapetz
<ma...@smartcvs.com> wrote:
> Hi,
>
> we are currently evaluating possibilities for building a java-based SVN
> client, still unsure if to use javahl or not. After reading the SVN book, I
> got some uneasy fealing about the future of svnserve, which could be one
> starting point for developing a pure java client library. Is the
> Apache/WebDAV combination the favoured server component and svnserve just
> some attachment for those who don't want to administer Apache? Would it be
> appreciated to push svnserve (at least for the first step) by such a client
> library or is it counterproductive regarding the future plans of SVN? And
> how important is or should be the role of SVN as WebDAV backend?
>
> Thanks in advance for any ideas on this topic.
I'm not sure where you're getting your ideas about svnserve having any
kind of 'uneasy' future, but it's simply not true. svnserve is just
as supported as mod_dav_svn/apache, and will continue to be supported
for the forseeable future. Personally, I make use of svnserve far
more often than I do mod_dav_svn/apache for my own repositories, and I
suspect that is not all that uncommon.
-garrett
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
RE: Future of svnserve
Posted by Justin Erenkrantz <ju...@erenkrantz.com>.
--On Monday, July 5, 2004 8:45 PM +0200 Marc Strapetz
<ma...@smartcvs.com> wrote:
> As I wrote, we are evaluating pros and cons of developing a pure java client
> library -- and the number of users is the ultimate argument. From this point
> of view, which protocol would you suggest to start with?
Really, you'd have to eventually support both. svnserve might be a little
easier to implement at first as it's not dragged down by the WebDAV
complexities. However, you can probably get a jump start on the WebDAV RA
method by bootstrapping with a pure-Java WebDAV client library (say Slide).
Remember that the libsvn_wc code would be independent of the RA method - and
the WC code would be where the bulk of the work would lie in a pure-Java
solution.
As a datapoint, svn.apache.org uses ra_dav not ra_svn. I know we have a bunch
of users who use SmartCVS - so it wouldn't help our users unless ra_dav were
supported by a SmartSVN. ;-) -- justin
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
RE: Future of svnserve
Posted by Marc Strapetz <ma...@smartcvs.com>.
Thanks for your feedback. So for the beginning we will investigate svnserve
more deeply -- certainly coming back with a lot of new questions :)
Best regards,
Marc.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: Future of svnserve
Posted by kf...@collab.net.
"Marc Strapetz" <ma...@smartcvs.com> writes:
> I also didn't mean to treat svnserve as second-class citizen. I hope to find
> out whether the community (including users) favours one kind of server. I
> have a quite clear picture of where I would personally use svnserve, but I
> can't estimate the potential of the combination WebDAV/DeltaV/SVN. From what
> I read in your book, it sounds promising, because version control could
> spread to users, which normally would not make use of such technologies ...
>
> Do you expect both servers to be equally well accepted (at least for the
> medium-term)? No mod_dav_svn/apache hype, administrators refusing to open
> the svnserve-port, etc.?
No formal survey has been taken, as far as I know. But my impression
from watching the users@ and dev@ list is that it really is about
50/50. I would expect that to continue; and yes, expect both to be
equally well accepted.
> As I wrote, we are evaluating pros and cons of developing a pure java client
> library -- and the number of users is the ultimate argument. From this point
> of view, which protocol would you suggest to start with?
I don't think there's any obvious guidance to give here; one would
have to say "both" :-). Flip a coin, I guess.
-Karl
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
RE: Future of svnserve
Posted by Marc Strapetz <ma...@smartcvs.com>.
Hi Garrett,
Hi Ben,
I also didn't mean to treat svnserve as second-class citizen. I hope to find
out whether the community (including users) favours one kind of server. I
have a quite clear picture of where I would personally use svnserve, but I
can't estimate the potential of the combination WebDAV/DeltaV/SVN. From what
I read in your book, it sounds promising, because version control could
spread to users, which normally would not make use of such technologies ...
Do you expect both servers to be equally well accepted (at least for the
medium-term)? No mod_dav_svn/apache hype, administrators refusing to open
the svnserve-port, etc.?
As I wrote, we are evaluating pros and cons of developing a pure java client
library -- and the number of users is the ultimate argument. From this point
of view, which protocol would you suggest to start with?
Best regards,
Marc.
> -----Original Message-----
> From: Ben Collins-Sussman [mailto:sussman@collab.net]
> Sent: Monday, July 05, 2004 5:46 PM
> To: Marc Strapetz
> Cc: svn-dev-list
> Subject: Re: Future of svnserve
>
>
> On Mon, 2004-07-05 at 07:46, Marc Strapetz wrote:
> > After reading the SVN book, I
> > got some uneasy fealing about the future of svnserve
>
> What is it in the book that gives you an uneasy feeling about it?
>
> > Is the
> > Apache/WebDAV combination the favoured server component and
> svnserve just
> > some attachment for those who don't want to administer Apache?
>
> How about this paragraph in the book:
>
> "Note that Subversion, as an open-source project, does not
> officially
> endorse any server as "primary" or "official". Neither network
> implementation is treated as a second-class citizen; each server has
> distinct advantages and disadvantages."
>
> So I'm worried that you have the impression that svnserve is some sort
> of throwaway thing.
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: dev-help@subversion.tigris.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: Future of svnserve
Posted by Ben Collins-Sussman <su...@collab.net>.
On Mon, 2004-07-05 at 07:46, Marc Strapetz wrote:
> After reading the SVN book, I
> got some uneasy fealing about the future of svnserve
What is it in the book that gives you an uneasy feeling about it?
> Is the
> Apache/WebDAV combination the favoured server component and svnserve just
> some attachment for those who don't want to administer Apache?
How about this paragraph in the book:
"Note that Subversion, as an open-source project, does not officially
endorse any server as “primary” or “official”. Neither network
implementation is treated as a second-class citizen; each server has
distinct advantages and disadvantages."
So I'm worried that you have the impression that svnserve is some sort
of throwaway thing.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org