05-13-2003, 09:08 AM
2nd of June, 2003. Either that or sometime during the working week beginning 2nd of June.
If Blizzard have any sense (Oops, there goes the logic in the following observation...) then they wouldn't release it on a weekend. To do so may as well hire a team of angry Sumo wrestlers to jump up and down on the servers and then set them alight. The weekends are usually the busiest times, and the server load to accomidate thousands of eagre D2 fans downloading the patch is likely to be extremely detrimental to system stability. At least in the week there'll be those who are working and won't be able to download it until they get home in the evening, and it's not like the whole world is working 9-to-5 at exactly the same moment.
And of course if Blizzard had a little more sense then they'd forego tradition and put the patch up on ftp.blizzard.com and the other mirrors at exactly the same time they allow it to be automatically downloaded from Battle.net, as opposed to an unspecified date after. That way, if B.net starts to slow down, the automatic response from those getting the patch will be to head of the Blizzard's FTP server or another mirror and get it there, keeping the pressure nice and easy on poor old Battle.net.
And if they don't adopt a similar strategy to this, then they have all the sense of the roadkill that my sister ran over today.
If Blizzard have any sense (Oops, there goes the logic in the following observation...) then they wouldn't release it on a weekend. To do so may as well hire a team of angry Sumo wrestlers to jump up and down on the servers and then set them alight. The weekends are usually the busiest times, and the server load to accomidate thousands of eagre D2 fans downloading the patch is likely to be extremely detrimental to system stability. At least in the week there'll be those who are working and won't be able to download it until they get home in the evening, and it's not like the whole world is working 9-to-5 at exactly the same moment.
And of course if Blizzard had a little more sense then they'd forego tradition and put the patch up on ftp.blizzard.com and the other mirrors at exactly the same time they allow it to be automatically downloaded from Battle.net, as opposed to an unspecified date after. That way, if B.net starts to slow down, the automatic response from those getting the patch will be to head of the Blizzard's FTP server or another mirror and get it there, keeping the pressure nice and easy on poor old Battle.net.
And if they don't adopt a similar strategy to this, then they have all the sense of the roadkill that my sister ran over today.
When in mortal danger,
When beset by doubt,
Run in little circles,
Wave your arms and shout.
BattleTag: Schrau#2386
When beset by doubt,
Run in little circles,
Wave your arms and shout.
BattleTag: Schrau#2386