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

Re: [TSVN] bugtraq feature extension - another approach

From: Mark Phippard <MarkP_at_softlanding.com>
Date: 2005-02-21 22:07:14 CET

SteveKing <steveking@gmx.ch> wrote on 02/21/2005 03:49:13 PM:

> So here it goes:
> Subversion uses the DAV protocol. And a subversion client can talk to
> any standard DAV server as if it were a Subversion repository (at least
> the main commands would work). So why not make the issue tracker
> implement a small DAV server which serves only an XML file with the open

> issues?
>
> - The issue tracker provides a DAV server/Subversion repository with
> only one file in it: the XML file with the open issues.
> - That XML file would be included in the working copy with svn:externals
> - With every update, the XML file would be updated too, so it would
> always contain the most recent open issues.
> - TSVN would parse that XML file when showing the commit dialog. Without

> worrying about authentication, connecting to a server, timeouts, ...
> - The issue tracker could intercept the normal authentication Subversion

> does with every other Repository to find out the username. Then it could

> change the XML file right before the actual update takes place to match
> the authenticated user.
>
> So 'all' it takes to do that would be a DAV server or a subversion
> repository which serves the XML file to a Subversion client.
>
> I don't think it would be a big problem for an issue tracker to just
> provide one XML file for all users - a simple script run after every
> change to any issues which re-generates the XML file and commits this to

> a repository would be enough. But it might be hard to serve that XML
> file 'on-the-fly' customized for the authenticated user.

If Subversion were capable of just doing an HTTP GET to retrieve the file
so that you did not need DAV, then I could maybe see this. Although I
think having a local file to base this on has it's own problems like
out-of-date problems.

I also just cannot see using a Subversion repository for this. In a large
open source project, or an Enterprise system there is just too much issue
churn.

What would you do with the XML file to filter it? We have thousands of
open issues in our system.

Mark

_____________________________________________________________________________
Scanned for SoftLanding Systems, Inc. by IBM Email Security Management Services powered by MessageLabs.
_____________________________________________________________________________

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Mon Feb 21 22:07:55 2005

This is an archived mail posted to the TortoiseSVN Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.