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

should we really ship serf as default for 1.7? (was: Re: serf and sourceforge.net don't get along)

From: Stefan Sperling <stsp_at_elego.de>
Date: Fri, 24 Jun 2011 15:06:28 +0200

On Wed, Jun 22, 2011 at 09:17:37PM -0400, C. Michael Pilato wrote:
> On 06/22/2011 07:30 PM, Daniel Shahaf wrote:
> > Bolstridge, Andrew wrote on Wed, Jun 22, 2011 at 14:51:37 +0000:
> >> Absolutely. The first thing to do is provide serf as a 2nd option,
> >> make a big song and dance about how great it is, and basically
> >> advertise the fact that it is there (from a user perspective).
> >
> > Didn't we do it as early as the 1.4 release notes?
> Well... not really. We've been referring to ra_serf as an "experimental DAV
> access module" for quite some time, as recently in release notes as 1.5 and
> certainly with no fanfare then or since.

I am still uneasy about this.

Given the number of issues that have been filed against ra_serf recently,
and issues that I've personally been running into when using it (all
reported to dev@), I am still not convinced that ra_serf is stable
enough to be the default for 1.7.

I think we should still give it some more time to mature, and expose it to
more testing on a variety of platforms by encouraging users to try it out.
After all, they will get a performance gain if they use it.
So we could use that as an incentive.

The responsible thing to do here is to favour stability over performance.
Sure, we cannot get rid of all the bugs before release, and the bugs
will be fixed earlier if ra_serf gets more exposure. But it would be
a disservice to our users if we released it as the default RA mechanism
if it isn't as stable as ra_neon.

Because the http-library is a client-side configuration setting,
some organisations would be having a very hard time getting all
of their users to use neon in case they run into problems with serf.

All that said I am very happy to see ra_serf bugs getting fixed quickly.
There is a lot of activity in serf land again now that the release is
approaching, and that is very good.
There is no question that serf is the going to be the default RA layer
at some point in the future. The question is just if now is the right time.
Received on 2011-06-24 15:07:16 CEST

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.