Bert Huijben <bert_at_qqmail.nl> writes:
> Could you please add some documentation to this function on when to
> pass an error_id and when to pass an apr_status. I was expecting that
> they were the same thing and most callers pass neither (just 0).
> Is it possible to fold the few cases where we use an error id into a
> specific (new?) Apr status?
> -----Original Message-----
> From: "philip_at_apache.org" <philip_at_apache.org>
> Sent: 18-6-2015 13:02
> To: "commits_at_subversion.apache.org" <commits_at_subversion.apache.org>
> Subject: svn commit: r1686181 - in /subversion/trunk/subversion/mod_dav_svn:./ reports/
> Author: philip
> Date: Thu Jun 18 11:02:24 2015
> New Revision: 1686181
> URL: http://svn.apache.org/r1686181
> Add an apr_status_t parameter to dav_svn__new_error() and
> dav_svn__new_error_svn(). This allows us to avoid dropping the
> status when ap_fflush() and ap_pass_brigade() calls fail, and a
> few other calls as well. Most calls currently pass zero.
These functions are wrappers around mod_dav functions and our
documentation already refers to mod_dav. I suppose we could duplicate
the information but mod_dav would remain definitive.
const char *desc);
My understanding is:
- 'status' is the HTTP status returned to the client
- 'error_id' is an additional DAV error, i.e. some violation of the
DAV rules. There are some definitions in mod_dav.h but callers can
pass other values.
- 'aprerr' is any underlying APR error, i.e. some sort of runtime
Philip Martin | Subversion Committer
WANdisco // *Non-Stop Data*
Received on 2015-06-18 13:39:09 CEST