For (b), and I think we've talked about this before, maybe we should keep a valid copy of version.xml in a known location at dqsd.net instead? This means more work for release management, since it has to be copied over, but it's no big deal (I'm doing the work anyway ;)).
I think we (i.e. you!) should do this. I don't think it's SF-friendly to pull that file for every user at every boot anyway. Forgetting to do the update at release time isn't a big deal anyway, because it just means people won't get the automatic update notification (until someone remembers).
We'll might also be able to get an idea of how many people are using it from the server stats on that file...
Will
------------------------------------------------------- This SF.net email is sponsored by: Perforce Software. Perforce is the Fast Software Configuration Management System offering advanced branching capabilities and atomic changes on 50+ platforms. Free Eval! http://www.perforce.com/perforce/loadprog.html _______________________________________________ DQSD-Devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dqsd-devel
