Web Development Blog

Comparission of 2010 and 2012 Olimpics' websites.

With respect to server side and client side technologies.

Vancover 2010:

Uses html with embedded pictures and videos. Client side.

The drop down menus are implemented using some sort of scripting language, most likely JavaScript, which is done client side, without the need to load a new page from the server.
The entire menu is loaded upon initial loading of the page, but is only shown when the script running in browser detects mouse over the section. Client side.

News section is dynamic by design and is generated server side as it gets updated, with the browser displaying the result in real time, constantly checking to load new articles. Server side.

The embedded video can be played on the server side, with the file itself being stored on the server and only streamed when the client side script detects the play command. Client and Server.

The three menu lists bellow the main image/drop down menu area, display content pulled by the server side script from database, but are styled by client side html. Their interactiveness is implemented by client side scripting which send input to the server to generate the link to requested webpage. Client and Server.

London 2012:

This website uses the same template as the previous one, changing it ever so slightly.
It adds a reel of videos above the results and search menus is build using client side scripts that allow viewer to see different videos available without loading them all from server. Once the chose which one to view, it is the server that generates and renders the video.

The list of links to other years’ websites is styled using JavaScript that checks for mouse interaction, but the images and links are written in html and are static.



I'm sorry, but we no longer support this web browser. Please upgrade your browser or install Chrome or Firefox to enjoy the full functionality of this site.