On Fri, Nov 30, 2012 at 1:52 AM, C. Michael Pilato <cmpilato_at_collab.net> wrote:
> [I'm going to try to summarize the body of responses generated from this
> original query -- a conversational reset, if you will -- so as to keep this
> line of inquiry moving toward closure.]
>> 3) libsvn_ra_serf stabilization. I know there have been a couple concerns
>> that Philip has raised (EAGAIN and the random failures).
> Philip and Ivan both seem keen on reinstating ra_neon.
While I was strongly against making ra_serf as default in svn 1.7, I
don't remember that I suggested to reinstate ra_neon.
I believe that most of the issues comes from the skelta mode (XML
report with many PROPFINDs/GETs) update editor implementation in
So compromise solution is to implement non-skelta mode in ra_serf and
make it default in svn 1.8. In this case some issues will be solved
* handling events on each open connection regularly.
* handling "408 Request Time-out" responses
* growth of server logs, expanded number of server connections
We already reduced number of requests for 1.8 servers, so may be we
can choose to use "skelta mode" for 1.8 servers and non-skelta
(ra_neon style) for pre-1.8 servers?
> OWNERSHIP: I can claim ownership of the ra_serf side of things if
> Lieven and Ivan (or others) can step up to advise me and to cover the
> Serf part itself.
I'm ready to help you!
Received on 2012-11-30 15:45:50 CET