Client-server applications, WebSocket, WebRTC...

WebSocket demo
We let communicate the browser's WebSocket standard object with a framework on the server or a local machine, to exchange texts or images.

WebRTC vs. WebSocket
With WebRTC the application get real-time access to data on the server. As well as WebRTC WebSocket have a JavaScript interface for standardized by the W3C which will facilitate their widespread use in browsers.

XMLHttpRequest vs. WebSocket
A new modernized standard ways to access the server, with WebSocket we obtain a two-way access to the server which can send notifications.

JSON or XML, which format to choose?
The XHR object loads directly an XML file with responseXML and a JSON file as a text with responseTxt.
Code to load either format with XHR or Fetch.

Tutorials and demonstrations of Fetch and Websocket are available on Webassembly.fr.

Ajax

The Anaa framework

Ajax is still the best solution for updating web content at the request of the user without using Promise, but Fetch is a simpler alternative to load resources and it is replaced by WebSocket and WebRTC for creating interactive applications online or local on a client-server model.

Anaa
A lightweight and easy to use library to make Ajax pages without to load a full framework.

Which interface for a modern application?
Comparison of various solutions: JavaScript and HTML, C# and XAML, Java and JavaFX, Qt and QML.

Archive

Ajax and Gears. Working offline with the Gears library.

Google's standard for accessing dynamic content (for history)
Google made a proposal for a standard to access dynamic content generated after the initial loading of a page.