> -----Original Message-----
> From: SteveKing [mailto:steveking@gmx.ch]
> Sent: 22 February 2005 20:45
> No bug tracking system would already have implemented serving
> an XML file as we need it. They would have to implement that anyway.
>
> 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
This might be naive of me to ask, but why can't TSVN store the user's bug
tracker authentication data as a setting, in the same way it stores the
user's SVN repo authentication data? Or, if it can, why _shouldn't_ it?
I mean, you're taking TSVN into a different area of function, with all of
this (very useful sounding!). When it's done, TSVN won't just be an
interface to Subversion repositories, it will be an interface to an issue
tracker too (or sometimes more than one - who wants to bet that some people
will want to use it on more than one project, and different projects use
different issue trackers? Pretty common, in the open source world...).
With that being the case, I think it's fair for TSVN to store such auth data
that it needs to perform its role.
Storing auth data would then both
- allow TSVN to filter the XML file of open issues for just those belonging
to the user.
- eliminate the possibility of an authentication dialog popping up (unless
the supplied data is wrong, in which case it can ask, and have a "remember
me" tickbox as with repo auth).
Peter Mounce
IML Ltd
e: mailto:petermounce_at_iml.co.uk w: http://www.iml.co.uk
t: (01428) 727476 f: (01428) 727011
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Wed Feb 23 10:53:28 2005