This is an old revision of this page, as edited by Dodger67(talk | contribs) at 09:21, 27 September 2014(Added tags to the page using Page Curation (copy edit, external links, cat improve, essay-like)). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.Revision as of 09:21, 27 September 2014 by Dodger67(talk | contribs)(Added tags to the page using Page Curation (copy edit, external links, cat improve, essay-like))
The opportunities for computing on the Web have been noted as far back as 1997.[1] It didn't take long before Web Computing was understood specifically as computation distributed to web clients.[2] Modern exploitations of this concept are generally focused on the Web Browser as the ultimate web client, and range from distributed computing for web workers as illustrated by CrowdProcess, to the full use of the Web Browser's stack in QMachine,[3] and includes the embedding of Web Applications as Semantic Hypermedia components.[4] The global approach of this distribution makes Web Computing a natural complement to Cloud Computing, where its server-side components tend to be hosted. The articulation typically places minimal computational load on the server-side, often Cloud-hosted, RESTful web services. An extreme example of this light server-side articulation of Web Computing is found in the role of the Signaling Server in Peer-to-peer networks set via WebRTC.
References
^Furmanski W (1997). "Petaops and Exaops: Supercomputing on the Web". IEEE Internet Computing. 1: 38–46. doi:10.1109/4236.601097.
This article needs additional or more specific categories. Please help out by adding categories to it so that it can be listed with similar articles.(September 2014)
