> -----Original Message-----
> From: Arfrever Frehtes Taifersar Arahesis
> Sent: woensdag 19 augustus 2009 15:05
> To: Stefan Sperling; dev_at_subversion.tigris.org
> Cc: Paul Burba
> Subject: Re: Issues with serf, scheduled for 1.7.0
> 2009-05-27 20:36:26 Stefan Sperling napisał(a):
> > On Wed, May 27, 2009 at 02:11:46PM -0400, Paul Burba wrote:
> > > Due to some problems with the dev_at_svn.t.o mailing list, Stefan
> > > Sperling can't create any new threads at the moment, so I'm doing
> > > for him.
> > Thanks Paul!
> > *grabs mic*
> > Yes, jackr is investigating. For some reason the dev list does
> > not want mail from me unless an in-reply-to header pointing
> > to the dev list is set... or something... we still don't really know.
> > So what I wanted to say was this:
> > Just poking serf people:
> > There has been talk of making serf the default HTTP backend for
> > It is the default in trunk right now, IIRC.
> > But there are two blocking issues for serf becoming the default
> > in 1.7.0, and nobody seems to be working on them:
> > #3375: ra_serf desperately needs an error handling overhaul
> > http://subversion.tigris.org/issues/show_bug.cgi?id=3375
> > (this one might be a bit of work)
The plumbing noted in this issue is done.
There are still several network triggerable SVN_ERR_ASSERT()/SVN_ERR_MALFUNCTION() calls that should be removed, but returning errors is much easier from most code paths. This work removed at least a dozen error leaks.
> > #3301: Cannot build without OpenSSL
> > http://subversion.tigris.org/issues/show_bug.cgi?id=3301
> > (this one should be easy)
> This also must be fixed:
> Serf Issue #28: Serf doesn't work with non HTTP/1.1 proxies
Received on 2009-08-19 15:40:00 CEST