Good catch! It seems entirely dead... It's probably related to the news at [1].
Yes, I had a quick look and concluded 'SF CVS probably broken', but couldn't be bothered to wade through it.
They are apparently upgrading the CVS storage, so presumably the node containing DQSD is temporarily off-line.
I think this raises the following issues:
1. Is a complicated CGI script doing a CVS checkout against a repository we don't manage a good way to provide a little bit of XML to every DQSD user at every start up? (That's a leading question - I think it might be better if the current version.xml was at something straightforward like <www.dqsd.net/version.xml>)
2. Is having an automatic synchronous HTTP fetch which can block the whole Explorer a good idea? I feel that maybe something here has changed with the most recent IE updates, and maybe it didn't used to block like this? Even with a short timeout (say a couple of seconds), I don't think that blocking the shell is at all OK.
I propose the following changes:
1. Place a current copy of the version.xml file onto the website, outside CVS 2. Change version.js to look there for it. 3. Disable automatic version checking by default (leave the manual check)
I don't think the automatic check should be put back in until we can do it in a non-blocking fashion.
What do people think?
Cheers,
Will
------------------------------------------------------- This SF.net email is sponsored by: SF.net Giveback Program. SourceForge.net hosts over 70,000 Open Source Projects. See the people who have HELPED US provide better services: Click here: http://sourceforge.net/supporters.php _______________________________________________ DQSD-Devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dqsd-devel
