This could be your banner!
If you’re like me, you waited with betted breath waiting for the keynote to start. Once it did, we all were met with the now infamous image (shown above) for a good chunk of the Keynote. Refreshing the page was met with either an “access denied” error or a blank page.
Dan Rayburn at StreamingMediaBlog.comshares his insight of what caused Apple’s major announcement video stream to botch itself throughout the show. According to Rayburn, it’s surprisingly not due to the number of viewers:
“The bottom line with this event is that the encoding, translation, JavaScript code, the video player, the call to S3 single storage location and the millisecond refreshes all didn’t work properly together and was the root cause of Apple’s failed attempt to make the live stream work without any problems. So while it would be easy to say it was a CDN capacity issue, which was my initial thought considering how many events are taking place today and this week, it does not appear that a lack of capacity played any part in the event not working properly. Apple simply didn’t provision and plan for the event properly.”
Whether or not the above was the cause of the problems, lets hope that it never happens again.
About Post Author
Advertisement
Share this via:
