Comet (programming): Difference between revisions

Revision as of 06:30, 12 June 2019

Revision as of 08:44, 7 July 2019

Line 107:

In April 2001, Chip Morningstar began developing a Java-based (J2SE) web server which used two HTTP sockets to keep open two communications channels between the custom HTTP server he designed and a client designed by [[Douglas Crockford]]; a functioning demo system existed as of June 2001.<ref>{{cite web|url=http://habitatchronicles.com/2009/09/elko-ii-against-statelessness-or-everything-old-is-new-again/|title=Elko II: Against Statelessness (or, Everything Old Is New Again)|first=Chip|last=Morningstar|date={{date|2009-09-06|dmy}}|website=Habitat Chronicles}}</ref>{{self published inline|date=December 2017}} The server and client used a messaging format that the founders of State Software, Inc. assented to coin as [[JSON]] following Crockford's suggestion. The entire system, the client libraries, the messaging format known as JSON and the server, became the State Application Framework, parts of which were sold and used by Sun Microsystems, Amazon.com, EDS and Volkswagen.<ref>{{cite web|url=http://habitatchronicles.com/2009/09/elko-i-the-life-death-life-death-life-death-and-resurrection-of-the-elko-session-sever/|title=Elko I: The Life, Death, Life, Death, Life, Death, and Resurrection of The Elko Session Server|first=Chip|last=Morningstar|date={{date|2009-09-05|dmy}}|website=Habitat Chronicles}}</ref>{{self published inline|date=December 2017}}

In March 2006, [[software engineer]] Alex Russell coined the term Comet in a post on his personal blog.<ref name="alex_comet">Alex Russell (3 March 2006). “[http://alex.dojotoolkit.org/?p=545 Comet: Low Latency Data for the Browser] {{Webarchive|url=https://web.archive.org/web/20080812034003/http://alex.dojotoolkit.org/?p=545 |date=2008-08-12 }}”. Alex Russell’s blog. Retrieved 29 November 2007.</ref> The new term was a play on [[Ajax (programming)|Ajax]] ([[Ajax (cleanser)|Ajax]] and [[Comet (cleanser)|Comet]] both being common household cleaners in the USA).<ref>{{cite web

|url=http://www.eweek.com/c/a/Application-Development/Microsoft-Scrubs-Comet-from-AJAX-Tool-Set/

|title=Microsoft Scrubs Comet from AJAX Tool Set

Line 125:

===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 | dead-url = yes }}</ref>

Specific techniques for accomplishing streaming Comet include the following:

Line 208:

==External links==

* [https://web.archive.org/web/20080104091304/http://cometdaily.com/ Comet Daily] – a website dedicated to articles on Comet techniques

* [https://web.archive.org/web/20080330033520/http://cometdaily.com/maturity.html Comparison of several comet server implementations]

{{DEFAULTSORT:Comet (Programming)}}