| Dear Ironmanlive.com |
[Apr. 13th, 2008|04:52 pm] |
|
Hire a couple IT people for Bob's sake. This isn't 1998; yes, high-volume servers aren't easy, but it's not exactly a new problem. And it's not the first (or twentieth) time you've had to deal with this. I fail to believe budget's a huge problem. |
|
|
| Comments: |
they don't even need to pay I imagine - with so many IT geeks being into IM, it shouldn't be that hard to get someone to help them out for some race schwag.
Heck, sure, streaming the live feed requires some bandwidth, but the static text race updates and they're running out of DB connections? SAD.
From: (Anonymous)
2008-04-13 10:15 pm (UTC)
Re: Shit... | (Link)
|
so it's not just me that can't see ironmanlive.com
![[User Picture]](http://l-userpic.livejournal.com/7637069/874282) | From: ![[info]](http://l-stat.livejournal.com/img/userinfo.gif) xomox
2008-04-13 11:10 pm (UTC)
Re: Shit... | (Link)
|
So, I've been following several people throughout the day, and I have each of their result pages in a different tab, reloading every so often. As usual, the results there are 2+ hours seperated from reality; that I'm used to. Just now, I went to reload one of the tabs (reload until it gives actual data, that is), and it came back with info. Info rolled back an additional three hours, putting whyiron back on the bike, still on his second bike loop. That's Bad.
Amen, brotha. This is not rocket science. | |
