NSLog();

Inside Apple’s Live Event Stream Failure, And Why It Happened: It Wasn’t A Capacity Issue

Unlike the last live stream Apple did, this time around Apple decided to add some JSON (JavaScript Object Notation) code to the apple.com page which added an interactive element on the bottom showing tweets about the event. As a result, this was causing the page to make refresh calls every few milliseconds. By Apple making the decision to add the JSON code, it made the apple.com website un-cachable.

Read the comments on the article above for more depth. Some people don't agree with the theories espoused in the article. For example, one starts off:

I would not give the author any credibility here. He speaks as if he understands dynamic web applications, but fails to understand the difference between JSON, JavaScript and AJAX.

Another:

Quick question then. If the problem was with the code on the webpage, how come this happened on every platform? Meaning, even on the Apple TV.

Another:

The web stream, after about half an hour, started to work flawlessly. Unless you claim that Apple completely rewrote the web page code in that time, I don't see how your theory could possibly be correct. And as others here have noted, the AppleTV feed also had issues, although the faulty page coding you blame was not part of it.

In other words, the article is junk, but the comments are gold.

P.S. My stream worked after about 30 minutes as well.

Comments RSS