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

Re: [PATCH] ra_serf and APR_EAGAIN handling

From: Justin Erenkrantz <justin_at_erenkrantz.com>
Date: Tue, 12 Jun 2012 14:00:50 +0200

On Tue, Jun 12, 2012 at 1:56 PM, Lieven Govaerts <lgo_at_mobsol.be> wrote:
>> How is it supposed to retry?  ra_serf needs to let the context_run
>> loop execute again to pull off the remaining bits from the socket.
>> Without the patch, we treat EAGAIN as a fatal error and it gets
>> returned all the way to the client.  -- justin
>
> Hm, I see now, it's not the return code of the response handler here,
> but the apr error wrapped in the svn error object.

Right.

> So why would we insist on treating EAGAIN as error in the response
> handler? There doesn't seem to be any added value of passing this
> expected return code as error all the way back to the look.

So, what should we do when EAGAIN is returned by the socket? The code
needs to know to run the loop again...without triggering a fatal
error.

I've never felt we got the error handling quite right in
serf...*headbang* -- justin
Received on 2012-06-12 14:01:22 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.