SteveKing <steveking@gmx.ch> wrote on 02/22/2005 03:44:44 PM:
> Mark Phippard wrote:
> > Even if it did work, I am not sure I would agree we are good to go in
the
> > sense that there isn't a single bug tracking system in the world that
> > actually supports this. Where as, at least if you were doing an HTTP
> > scraper, it would work with any read-only HTTP-based systems just
fine.
>
> No bug tracking system would already have implemented serving an XML
> file as we need it. They would have to implement that anyway.
I guess I did not realize that you only planned on receiving a specific
XML file. Since you were talking about this in the context of RegEx, I
thought you were planning on receiving the same HTML file a browser
receives and use RegEx to extract the issues. That is why I kept
referring to it as HTTP-scraping. I agree that if we are going to define
a new XML format and expect bug trackers to support it, then it is no
different.
> But still, if we don't do it that way but fetch the XML file directly
> from the commit dialog, then we have the same problems I mentioned when
> I started this thread:
>
> - how to get the username to filter the list of open issues
> - how to prevent an authentication dialog interrupting the user
I still think the solution I proposed is better. In my solution, TSVN is
just putting a framework in place that the bug tracker has to fill on the
client. TSVN could provide a default implementation that would work with
unauthenticated XML, but anything else leaves it to the bug tracker.
While it is probably more difficult to build an integration on the client
side, I think it is better since one person can write a smallish client
program that anyone using Bugzilla or Tigris can use. Where as a
server-side solution requires Bugzilla, Tigris etc. to write it, and make
it available on your project. For example, how long before SourceForge or
the other bug hosting sites provide this to projects they host, even
assuming that their underlying issue trackers are enhanced for it. But
one motivate programmer can solve it for all SourceForge projects on the
client.
Also, having a client-side program pushes the issue of things like
authentication on to someone else, and also opens the door for supporting
non-HTTP solutions.
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 Tue Feb 22 21:58:05 2005