Actually, about 8GB was transferred in about 18 minutes, before pair.com's web server crashed and couldn't handle the load, and I received an email telling me that my files were being "locked".
Quoted from an email I received from pair.com technical support:
Because of the requests for these files, no other site hosted on the entire
server was able to accept request due to the saturation to and from your
server.
And lastly, your account transferred about 8 GB of data in 18 minutes.
So, 3 thoughts come to mind:
1. What bill? pair.com drops the day with the most-used bandwidth when calculating billing!
2. The files were quickly moved to University web servers which handled the load fine.
3. It's interesting that a pair.com support rep posted my account statistics in a public forum.. hmmm.
Slashdot Mirror
Actually, about 8GB was transferred in about 18 minutes, before pair.com's web server crashed and couldn't handle the load, and I received an email telling me that my files were being "locked".
Quoted from an email I received from pair.com technical support:
Because of the requests for these files, no other site hosted on the entire server was able to accept request due to the saturation to and from your server.
And lastly, your account transferred about 8 GB of data in 18 minutes.
So, 3 thoughts come to mind:
1. What bill? pair.com drops the day with the most-used bandwidth when calculating billing!
2. The files were quickly moved to University web servers which handled the load fine.
3. It's interesting that a pair.com support rep posted my account statistics in a public forum.. hmmm.
This kind:
m da-iii.html
:-)
http://www.digit-life.com/articles2/pda/t-mobile-
mp3 and wav files moved to University webspace -- should be able to withstand the /.ing.
cheers.