[From nobody Mon Mar 25 16:15:48 2013
From: "Marc van Woerkom" <q5480035@mailstore.fernuni-hagen.de>
Subject: Re: Web interface framework for Erlang and J-EAI
To: Mickael Remond <mickael.remond@erlang-fr.org>
X-Mailer: CommuniGate Pro Web Mailer v.4.0.6
Date: Tue, 05 Jul 2005 12:11:30 +0200
Message-ID: <web-11497852@mailstore.fernuni-hagen.de>
In-Reply-To: <42CA57DD.30609@erlang-fr.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="ISO-8859-15"; format="flowed"
Content-Transfer-Encoding: 8bit

>The web is slowly moving to some kind of "connected" 
>protocol to replace HTTP. This is what has been called 
>AJAX, but we are only at the beginning of the movement. 
>We have "web pages" that basically are client that 
>refresh themselves while being connected to a back-end 
>server.
>J-EAI (and more generally XMPP) can handled this 
>connected part very nicely. This is a bus that can 
>distribute XML stream to connected client (or put some 
>info in message queue if needed).
>
>As a transition, xe can use standard HTTP to distribute 
>the web pages application (Javascript). They can then 
>connect to a J-EAI bus to get and send realtime event 
>from the back-end server and refresh its view.

The central idea of those AJAX applications IMHO is not
getting rid of HTTP.

What they do is avoiding page transitions!

The classic cycle is
- display page
- get new data
- display page
- get new data
- display page
etc.

What we now see are web apps that take web browser like 
IE 6, Mozilla, Opera and Safari as granted, which
expose the rendered HTML page as an elaborate DOM tree.
E.g. a sub image of a Google maps page is available as DOM 
object, and embedded Javascript on that page sees this
image as object and the Javascript code is able to 
manipulate this image object via various means.

When the user interacts, that Javascript can ask new
data from the server in the background, be it via XML
protocol (the "x" in AJAX) or via a simple HTTP request
(as featured in a complicated web app developed at my
  company).

Once the data came in, the Javascript shovels that
data directly in the image object and the browser
updates the display with out the need for rerendering
the whole page display.

Regards,
Marc

]