Wonder how this could suddenly happen as WRC.com has been providing live times and splits for years now...
Very poor, especially coinciding with ALL LIVE on Monte Carlo (which wasnt) and didnt show many splits.
Printable View
Anybody who's ever looked at the codebase for WRC+ can tell it's amateur hour over there. Heck, even the site design for wrc.com looks like something a high schooler made on Microsoft Frontpage 15 years ago. But they're getting better, slowly.
Miss-integration between two services is well explained?
This is something that a lot of services have trouble with after starting out or making major changes and I just can not understand it. How can they let this happen? The amount of requests can't be a surprise for them, they must have some previous data and be able to calculate a safe buffer.Quote:
At more than 3 million requests per hour, the public-facing API became overloaded
Still, non of the issues that revealed themselves during the launch was a surprise and I'm quite confident it will be stabilized quite quickly.
"Unfortunately, WRC.com's systems and ours were not integrated correctly, and traffic from the spectating public was forwarded to our servers. At more than 3 million requests per hour, the public-facing API became overloaded. WRC.com was temporarily disabled in order to allow the rest of our clients - including the AC de Monaco - stable access to timing information. Since then, we've worked with WRC.com to ensure the problem isn't repeated"
What more do you need to know? The names of the people at WRC.com who screwed it up?
Well, I guess that's what happens if I start reading and commenting before finishing my first coffee. Somehow I totally missed that part, thanks for bolding it our for me.
No need for the names of the people in WRC who screwed up, as it seems I was the one who screwed up even the most basic task of reading.
So if I understood correctly the WRC site was constructed in a way that every time you reloaded the splits page it made a request to the RallySafe API to load the times, whereas they could and should have had just one connection from the WRC site to RallySafe API and saved the times to WRC site for the public requests. The WRC site can handle heavy traffic, RallySafe API is not designed for that.
Interesting interview with Wayne Christie, new president of FIA Rally commission: https://rallysportmag.com/interview-...es-commission/
Toyota team museum. https://rallysportmag.com/aladins-ca...-museum150218/