Greg Hudson <ghudson@MIT.EDU> writes:
> On Wed, 2002-11-27 at 14:29, Ben Collins-Sussman wrote:
> > I don't understand the problem. If your server process is linking
> > against libsvn_fs (which it must be), then it has access to the whole
> > APR error system and SVN error system (which is just an extension.)
> > Why not just move apr error codes over the wire?
>
> The goal is to marshal and unmarshal an svn_error_t structure over the
> wire. The apr_err field is portable, but the src_err field is not.
>
> > FWIW, mod_dav_svn marshalls the error code to the client in an xml
> > structure. You can do something similar, no?
>
> It looks like ra_dav punts on the src_err field (always sets it to 0).
> I guess I can do the same.
Yah, I'd do that. It's very rare to even *have* a src_err in an
svn_error_t structure; most errors are originally generated by the svn
libs. When they do get a src_err, they usually just wrap it up with
an apr_err anyway. At a minimum, you can have your server process
dump the src_err to a logfile.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Nov 27 21:42:06 2002