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

Re: Suggestion: "svn explain"

From: Karl Fogel <kfogel_at_newton.ch.collab.net>
Date: 2002-08-05 18:18:45 CEST

Greg Hudson <ghudson@MIT.EDU> writes:
> On Sun, 2002-08-04 at 11:54, cmpilato@collab.net wrote:
> > That is precisely the plan. We need to group our error codes into
> > those that can be sent across the wire, and those that can't, leaving
> > empty error slots between the groups.
> Pardon my confusion here--shouldn't DAV or DeltaV specify error codes
> for the wire protocol, and not us?

Oh, these aren't protocol errors. The problem here is how to get a
filesystem error from the server to the client, so the client can
correctly report it to the users.

DAV can wrap up those errors any way it wants, so long as the client
is able to unwrap and report the right thing reliably.

An example: when the server bounces back with a "Transaction out of
date" error, the client needs to tell the user that's what happened.


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Aug 5 18:34:07 2002

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.