Contents

Web development

Front-end Development Process

What is Web 2.0?

Beyond REST

It's Too Darn Hot

Ajax vs Comet

In the original request-response model of the Web, a browser receives a complete Web page in response to each request.

Ajax was invented to overcome this overhead by doing away with the need to receive a new page and instead simply request a data response from the server. However, Ajax is still a request-response model, and since Ajax requires that the client initiates each interaction, data cannot be sent at will from the server. To get round this problem, Ajax applications often use polling to detect new information on the server, but this often results in unacceptable loads on the server and client.

Comet is a 'push' approach, greatly improving throughput and decreasing latency and server load. Once the client has made the initial connection, the server sends updates as they occur, without the client needing to issue further requests. See the figure above for a comparison of Ajax and Comet data transfer.

Why do you need DAta Portability

DataPortability - Connect, Control, Share, Remix from Smashcut Media on Vimeo

Open ID explication

Gforge architecture

Authentication for Web Applications

Stumbleupon architecture

Amazing possibilities with Google Docs

Differents between Prototype & JQuery

http://www.slideshare.net/remy.sharp/prototype-jquery-going-from-one-to-the-other

Web Trends

http://www.lipsum.com/

Market Share for Top Servers Across All Domains August 1995 - May 2007

Dojo.Storage Test

Further information in: http://codinginparadise.org/projects/dojo_storage/release/dojo/tests/storage/test_storage.html