Wednesday, October 27, 2004

The Gmail Engine : How they do it!

You've probably noticed that Gmail's interface is extremely fast when compared to other web-based email systems like Yahoo! Mail and Hotmail. This is a result of Gmail's placement of the UI engine on the client-side as a JavaScript module. Whenever you log in to Gmail, a copy of the UI engine is loaded into one of the HTML page frames and remains there for the duration of your session (credit has to be given to Oddpost for being the first ones who perfected this idea). Subsequent actions from the Gmail interface are then routed through the Gmail UI engine in your browser, which in turn makes HTTP requests (via the XmlHttpRequest object) to the Gmail server, interprets the DataPack, and updates the UI dynamically. In contrast, Hotmail and Yahoo! Mail follow traditional web application models and reload the entire UI after almost every action.

I know its rather old, but I just learnt it today and thought I'd share it.


At 10:58 AM, Anonymous Anonymous said... just a kind of nubie on web based programming world, do you have any idea which one the best webmail interfaces other than squirrelmail that able to work as fine as gmail?..our users had a lot of messages in their mailboxes and problems coloring my day everytime they try accessing their mail through the web caused by shorting process between the webmail and Imap take too long and sumtimes it was timed out, all i need to do is no matter how long it'll takes time for webmail to fetch the mail header, but don't tell our users error messages like "Connection Droped by Imap Server"..or "Too many messages"...or even "Connection Timed Out" is really good gmail engine available to download?..hehe..sorry just a comment..but you post a good thread mon..thanks. (xparacetamol at gmail dot com


Post a Comment

<< Home