Content deleted Content added
m →Alternatives: Fix supported browsers |
m Task 16: replaced (3×) / removed (0×) deprecated |dead-url= and |deadurl= with |url-status=; |
||
Line 55:
|date = 2005-11-01
|accessdate = 2008-05-06
|
|archiveurl = https://web.archive.org/web/20060208041559/http://www.obviously.com/tech_tips/slow_load_technique
|archivedate = 2006-02-08
}}
</ref> The term ''Comet'' is not an acronym, but was coined by Alex Russell in his 2006 [[blog]] post ''Comet: Low Latency Data for the Browser''.<ref>{{cite web
Line 73 ⟶ 72:
===Early Java applets===
The ability to embed [[Java applet]]s into browsers (starting with Netscape 2.0 in March 1996<ref>{{cite web |url=http://www27.netscape.com/comprod/products/navigator/version_2.0/index.html |title=Netscape.com |accessdate=2017-08-16 |
===The first browser-to-browser communication framework===
Line 127 ⟶ 126:
===Streaming===
An application using streaming Comet opens a single [[persistent connection]] from the [[Web browser|client browser]] to the server for all Comet [[Event (computing)|events]]. These events are incrementally handled and interpreted on the client side every time the server sends a new event, with neither side closing the connection.<ref name = "WRC">{{cite web | url = http://www.webreference.com/programming/javascript/rg28/ | title = Comet Programming: Using Ajax to Simulate Server Push | accessdate = 2010-10-20 | last = Gravelle | first = Rob | publisher = Webreference.com | archive-url = https://web.archive.org/web/20101018055530/http://www.webreference.com/programming/javascript/rg28/ | archive-date = 2010-10-18 |
Specific techniques for accomplishing streaming Comet include the following:
|