"Oren Eini (Murphy & Associates)" <v-orene_at_microsoft.com> writes:
> I think it belongs here. It is a dev issue, not a usage issue.
> More specifically, it regards the WebDAV protocol.
Oh, this list isn't for development in general. It's for the
development of Subversion itself -- that is, the code for which the
Subversion maintainers have consciously taken responsibility.
It's great to see someone else implementing Subversion or WebDAV
implementations, and we're happy to help... But on the users@ list,
because it's about the usage of Subversion and/or its APIs, not about
the development of Subversion. You are "using" the Subversion and/or
WebDAV protocols, hence "users@". If you were talking about a patch to
Subversion's own code, for example, then dev@ would be the place.
> Okay, more explanation.
> I am writing SVN Server. One that can use the WebDAV protocol and make
> SVN clients think that they are talking to Subversion repository.
> My question regards to how I can cause a server error message to be
> shown to the user.
> On certain situations, I can use the error codes and send my own
> message along. The problem is that in other situations (such as a GET
> request), sending an error message back to the client will not show
> the error to the user, but a generic error instead.
> I want to know if there is a way to send an error to SVN clients in
> such a fashion that it will always be displayed.
Well, I don't remember everything our server does to get the client to
displays errors, but have you sniffed the wire protocol for examples?
See http://subversion.tigris.org/faq.html#net-trace for more.
Best,
-Karl
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: dev-help_at_subversion.tigris.org
Received on 2008-03-07 19:52:45 CET