On Sat, Sep 13, 2003 at 01:02:55PM -0500, Ben Collins-Sussman wrote:
> Joe Orton <joe@manyfish.co.uk> writes:
>
> > > The obvious thing to do, we thought, was to start using
> > > ne_proppatch(). Presumably it search 207 repsonse bodies for errors.
> > > (Right, Joe?)
> >
> > It does, but you get all that by just using ne_simple_request() to
> > dispatch your custom request already; that's all that ne_proppatch()
> > does anyway. (the error handling is dumb, I presume you don't need to
> > know exactly what the error was in a useful way)
>
> Our current proppatch code calls ne_request_dispatch(), not
> ne_simple_request(). Maybe I should investigate switching over to the
> latter function. Will it be able to pull out a 500 error from within
> a 207 response?
Yes, exactly that - ne_simple_request() dispatches the request and
parses a 207 response if one is returned, returning NE_ERROR for either
a non-2xx response code, or a 207 response which had a non-2xx propstat
inside it anywhere.
(I notice there's an undocumented gotcha, ne_simple_request destroys the
request object too)
joe
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sun Sep 14 11:12:40 2003