When I tried to update my server yesterday, because ppl told be they're unable to connect with the new client, I found that the download servers were totally overloaded.
All I got was a HTTP 503.
after some time I was fed up and ended up writing this one:
Code:
ls -al asdasdasd # produce any error to set $?
while [ $? != 0 ]; wget http://ftp.4players.de/pub/hosted/ts3/releases/beta-23/teamspeak3-server_win32-3.0.0-beta23.zip; done
and it took nearly half an hour until the server managed to get me that file.
sorry, but even for free software such a dramatic change, that required server and client to be updated with only 1 day prior notice is in the best case bad planned, in the worst case just stupid.
You should at least have the server display a message a week before you push the client update, and allow the client to update itself automatically when it hits a server that already got the update.
Also the client has to deplay the incompatibility warning, not just the website.
The better solution would be of course to have the client and server compatble at any time. If there is a change in the protocol, the old protocol should still be supported (with warnings) for a month or so. That way nobody would get into any trouble, and you could roll out the update without totally killing the download servers.
also it would be nice to know how much downloads there were yesterday evening, just to see if it is somehow possible to create a mirror or something.