Will, > I still think it would be user- (possibly not now it's async) and > SF-friendly to move to using a version.xml which can be > served statically > rather than fetched out of their CVS repository every time.
Definitely - my only concern with that was that it may take a while before a new version.xml propagates from CVS to the actual site, but on the other hand, the installer and the version xml file will always be available at the same time. And we won't be updating it that often, will we? It changes the directions for building a release a little, so we will have to update src/ReadMe.txt when we get it in place. No biggie, just to keep it in mind. > It would have taken me a week to learn enough about > MSXML to have implemented that! I actually needed the exercise... I've been curious about MSXML's asynchronous loading for a while, but never had reason to use it. :-) Cheers, Kim ------------------------------------------------------- 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
