Yazı, özellikle birden fazla kullanıcının aynı veriyi değiştirdiği durumlarda ortaya çıkabilecek çakışmanın engellenmesi ile ilgili yeni bir kullanıcı-sayfa etkileşimi modelinden bahsediyor.
Regular Ajax improves the responsiveness of a UI for a single user, but at the cost of allowing the context to go â€œstaleâ€ for long-lived pages. Changes to data from others users is lost until a user refreshes the whole page. An application can alternately return to the â€œbad old daysâ€ and maintain some sort of state mechanism by which it tells client about changes since the last time theyâ€™ve communicated. The user has to either wait until they preform some action which would kick off a request to see the updated state from other users (which might impact the action they wanted to preform!) or request changes from the server at some interval (called â€œpollingâ€). Since the web is inherently multi-user, itâ€™s pretty obvious that regular Ajax imposes usability and transparency hurdles for users. Applications that employ the Comet technique can avoid this problem by pushing updates to all clients as they happen. UI state does not go out of sync and everyone using an application can easily understand what their changes will mean for other users. Ajax improves single-user responsiveness. Comet improves application responsiveness for collaborative, multi-user applications and does it without the performance headaches associated with intermittent polling.
Son cümle herşeyi özetlemiş aslında, ama ben feci okurum derseniz, Comet: Low Latency Data for the Browser