RE: [PATCH] operation logging

Greg Hudson Wrote :
> * Operations from 1.0 and 1.1 clients won't be logged. Having an
> incomplete log isn't very satisfying.

Then what about (re)considering the proposal to provide client API details
(as in version numbers) as a part of the mass of information that gets sent
to the server.

Providing sufficient hook the server admin can decide whether to 'put up'
with this lack of logging information (allowing the old client) or refusing
the transaction based on the user-agent

---------------------------------------------------------------------------

Steven Higgan - 3rd Year B.I.T. Otago Polytechnic, Dunedin New Zealand
.net geek

-----Original Message-----
From: Greg Hudson [mailto:ghudson@MIT.EDU]
Sent: Monday, 6 June 2005 1:51 p.m.
To: kfogel@collab.net
Cc: dev@subversion.tigris.org
Subject: Re: [PATCH] operation logging

Well, the obvious criticisms are:

  * Operations from 1.0 and 1.1 clients won't be logged. Having an
incomplete log isn't very satisfying.

  * You haven't solved the problem of how to log, say, a commit over DAV
once. You'll wind up logging it once for each HTTP operation involved
in the commit. For your patch this is no problem, since you're just
annotating the pre-existing HTTP log information, but for a generic
logging mechanism your proposal seems incomplete.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org

-- 
No virus found in this incoming message.
Checked by AVG Anti-Virus.
Version: 7.0.323 / Virus Database: 267.6.2 - Release Date: 4/06/2005
 
-- 
No virus found in this outgoing message.
Checked by AVG Anti-Virus.
Version: 7.0.323 / Virus Database: 267.6.2 - Release Date: 4/06/2005
 
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org