Jump to content

Real-time web: Difference between revisions

From Wikipedia, the free encyclopedia
Content deleted Content added
No edit summary
(43 intermediate revisions by 24 users not shown)
Line 1: Line 1:
{{Use dmy dates|date=September 2019}}
{{multiple issues|
{{multiple issues|
{{more footnotes|date=November 2010}}
{{more footnotes|date=November 2010}}
{{refimprove|date=November 2010}}
{{more citations needed|date=November 2010}}
{{essay|date=April 2015}}
{{essay|date=April 2015}}
{{Buzzword|date=July 2011}}xxdxxx
{{Buzzword|date=July 2011}}
}}
}}


The '''real-time web''' is a network web using technologies and practices that enable users to receive information as soon as it is published by its authors, rather than requiring that they or their software check a source periodically for updates.
The '''real-time web''' is a [[computer network|network]] web using technologies and practices that enable users to receive information as soon as it is published by its authors, rather than requiring that they or their software check a source periodically for updates.


==Difference from real-time computing==
==Difference from real-time computing==
The real-time web is fundamentally different from [[real-time computing]] since there is no knowing when, or if, a response will be received. The information types transmitted this way are often short messages, status updates, news alerts, or links to longer documents. The content is often "soft" in that it is based on the [[social web]]—people's opinions, attitudes, thoughts, and interests—as opposed to hard news or facts.
The real-time web is different from [[real-time computing]] in that there is no knowing when, or if, a response will be received. The information types transmitted this way are often short messages, status updates, news alerts, or links to longer documents. The content is often "soft" in that it is based on the [[social web]]—people's opinions, attitudes, thoughts, and interests—as opposed to hard news or facts.

==True-realtime web (an "alternate" model)==
From another point of view, the real-time web consists in making the client interface (or the web side; or the web layer) of a web application, to communicate continuously with the corresponding real-time server, during every user connection. As a fast pic of the client/server model, imagine each client object (each web module of the web [[GUI]] of an application) having its object class alive as a sub process (of its user session) in the server environment. In this scenario, the web is considered as the human entrance (interface) to the real-time environment: at each connected web URL, or Internet real-time zone, corresponds a different "front-end" web application. The real-time server acts as a [[logic network operating system]] for the programmable array of applications; handles the array of connected users for each application; attends for connections from real-world appliances and second level real-time servers. Applications behaviours and the intercommunication procedures between online services or applications, online users, and connected devices or appliances, are settled in the corresponding source code of each real-time service written in the real-time-interpreted programming language of the centric server.

As opposite to previous scenario, real-time web is exactly soft [[real-time computing]]: the round trip of a data ping-pong signal from the real-time server to the client must take about 1s (max) to be considered real-time and not to be annoying for humans (or users) during their connections. About the dispute between social web and real-time web, we can say real-time web is social by default and it is not true the contrary (WEB-r comes before Web 2.0). The WEB-r model is called [[true-realtime web]] to highlight the differences with the defective (de facto) model of real-time web generally perceived. From the industry point of view, this model of (general) real-time Internet can also be defined as [[electronic web]], that comes with the intrinsic meaning of not being limited to the web side of the Net, and with the direct reference to its server/rest-of-the-world perspective as a mechanism of a single clock.


==History==
==History==
Examples of real-time web are Facebook's newsfeed, and Twitter, implemented in social networking, search, and news sites. Benefits are said to include increased user engagement ("flow") and decreased server loads. In December 2009 real-time search facilities were added to [[Google Search]].<ref>{{cite web|url=http://googleblog.blogspot.com/2009/12/relevance-meets-real-time-web.html|title=Relevance meets the real-time web}}</ref>
Examples of real-time web are Facebook's newsfeed, and Twitter, implemented in social networking, search, and news sites. Benefits are said to include increased user engagement ("flow") and decreased server loads. In December 2009 real-time search facilities were added to [[Google Search]].<ref name=":0">{{cite web|url=http://googleblog.blogspot.com/2009/12/relevance-meets-real-time-web.html|title=Relevance meets the real-time web}}</ref>


The absolutely first realtime web implementation worldwide have been the WIMS true-realtime server and its web apps in 2001 (WIMS = Web Interactive Management System); based on the above WEB-R model; build in Java (serverside) and Adobe Flash (clientside). The true-realtime web model was born in 2000 at mc2labs.net by an Italian independent researcher.
The absolutely first realtime web implementation worldwide have been the WIMS true-realtime server and its web apps in 2001-2011 (WIMS = Web Interactive Management System); based on the True-RealTime Web (WEB-r) model of above; built in WIMS++ (server built in Java) (serverside) and Adobe Flash (ex Macromedia Flash) (clientside). The true-realtime web model was born in 2000 at mc2labs.net by an Italian independent researcher.


==Real-time search==
==Real-time search==
A problem created by the rapid pace and huge volume of information created by real-time web technologies and practices is finding relevant information. One approach, known as '''real-time search''', is the concept of searching for and finding information online as it is produced. Advancements in web search technology coupled with growing use of [[social media]] enable online activities to be queried as they occur. A traditional [[web search]] [[Web crawler|crawls]] and [[Index (search engine)|indexes]] web pages periodically, returning results based on relevance to the search query. [[Google Real-Time Search]] was available in [[Google Search]] until July 2011.
A problem created by the rapid pace and huge volume of information created by real-time web technologies and practices is finding relevant information. One approach, known as '''real-time search''', is the concept of searching for and finding information online as it is produced. Advancements in web search technology coupled with growing use of [[social media]] enable online activities to be queried as they occur. A traditional [[web search]] [[Web crawler|crawls]] and [[Index (search engine)|indexes]] web pages periodically, returning results based on relevance to the search query. [[Google Real-Time Search]] was available in [[Google Search]] until July 2011.{{Citation needed|date=November 2022}}


==See also==
==See also==
Line 31: Line 27:
*[[Meteor (web framework)|Meteor]]
*[[Meteor (web framework)|Meteor]]
*[[Microblogging]]
*[[Microblogging]]
*[[Mojolicious]]
*[[Node.js]]
*[[Node.js]]
*[[Prospective search]]
*[[Prospective search]]
*[[PubNub]]
*[[PubNub]]
*[[Push technology|Push Technology]]
*[[Push technology|Push Technology]]
*[[Scoopler]]
*[[Vert.x]]
*[[Vert.x]]


Line 42: Line 38:


==External links==
==External links==
*{{Cite news|url=http://www.guardian.co.uk/business/2009/may/19/google-twitter-partnership|title=Google 'falling behind Twitter'|last=Wray|first=Richard|date=19 May 2009|work=The Guardian|accessdate=17 June 2009}}
*{{Cite news|url=https://www.theguardian.com/business/2009/may/19/google-twitter-partnership|title=Google 'falling behind Twitter'|last=Wray|first=Richard|date=19 May 2009|work=The Guardian|accessdate=17 June 2009}}
*{{Cite news|url=http://www.nytimes.com/2009/06/14/business/14digi.html|title=Hey, Just a Minute (or Why Google Isn't Twitter)|last=Stross|first=Randall|date=13 June 2009 |work=New York Times|accessdate=17 June 2009}}
*{{Cite news|url=https://www.nytimes.com/2009/06/14/business/14digi.html|title=Hey, Just a Minute (or Why Google Isn't Twitter)|last=Stross|first=Randall|date=13 June 2009 |work=New York Times|accessdate=17 June 2009}}
*{{Cite news|url=http://online.wsj.com/article/BT-CO-20090615-712397.html |title=Internet Giants Look For Edge In Real-Time Search |last=Morrison |first=Scott |date=15 June 2009 |work=Wall Street Journal |accessdate=17 June 2009 |deadurl=yes |archiveurl=https://web.archive.org/20090616204058/http://online.wsj.com:80/article/BT-CO-20090615-712397.html |archivedate=16 June 2009 }}
*{{Cite news|url=https://online.wsj.com/article/BT-CO-20090615-712397.html |title=Internet Giants Look For Edge in Real-Time Search |last=Morrison |first=Scott |date=15 June 2009 |work=Wall Street Journal |accessdate=17 June 2009 |url-status=dead |archiveurl=https://web.archive.org/web/20090616204058/http://online.wsj.com/article/BT-CO-20090615-712397.html |archivedate=16 June 2009 }}
*{{Cite news|url=http://www.readwriteweb.com/archives/explaining_the_real-time_web_in_100_words_or_less.php|title=Explaining the Real-Time Web in 100 Words or Less|last=Kirkpatrick|first=Marshall|date=22 September 2009|work=ReadWriteWeb}}
*{{Cite news|url=http://www.readwriteweb.com/archives/explaining_the_real-time_web_in_100_words_or_less.php|title=Explaining the Real-Time Web in 100 Words or Less|last=Kirkpatrick|first=Marshall|date=22 September 2009|work=ReadWriteWeb}}

{{Use dmy dates|date=October 2010}}


{{DEFAULTSORT:Real-Time Web}}
{{DEFAULTSORT:Real-Time Web}}
[[Category:Real-time web| ]]
[[Category:Internet search]]
[[Category:Internet search]]
[[Category:Real-time web| ]]

Revision as of 19:52, 7 November 2022

The real-time web is a network web using technologies and practices that enable users to receive information as soon as it is published by its authors, rather than requiring that they or their software check a source periodically for updates.

Difference from real-time computing

The real-time web is different from real-time computing in that there is no knowing when, or if, a response will be received. The information types transmitted this way are often short messages, status updates, news alerts, or links to longer documents. The content is often "soft" in that it is based on the social web—people's opinions, attitudes, thoughts, and interests—as opposed to hard news or facts.

History

Examples of real-time web are Facebook's newsfeed, and Twitter, implemented in social networking, search, and news sites. Benefits are said to include increased user engagement ("flow") and decreased server loads. In December 2009 real-time search facilities were added to Google Search.[1]

The absolutely first realtime web implementation worldwide have been the WIMS true-realtime server and its web apps in 2001-2011 (WIMS = Web Interactive Management System); based on the True-RealTime Web (WEB-r) model of above; built in WIMS++ (server built in Java) (serverside) and Adobe Flash (ex Macromedia Flash) (clientside). The true-realtime web model was born in 2000 at mc2labs.net by an Italian independent researcher.

A problem created by the rapid pace and huge volume of information created by real-time web technologies and practices is finding relevant information. One approach, known as real-time search, is the concept of searching for and finding information online as it is produced. Advancements in web search technology coupled with growing use of social media enable online activities to be queried as they occur. A traditional web search crawls and indexes web pages periodically, returning results based on relevance to the search query. Google Real-Time Search was available in Google Search until July 2011.[citation needed]

See also

References

  1. ^ "Relevance meets the real-time web".