Use case - event-source

On Thu, 06 Sep 2007 11:59:06 +0900, Robert Burns <rob@robburns.com> wrote:

> EVENT-SOURCE [6]
> -------------------------
> For this element, I had great difficulty in deciphering the use cases  
> for it. Any discussion on this would be helpful.

To build Web Applications, it is nice if you can make them listen to  
things that happen outside the page. This can be done by just connecting  
to your server and checking whether you updated something.

The benefit that event-source offers is having a common standard for doing  
this (and format for the data). This means you can build a service or  
three, and other people can build clients to connect to them, without  
first negotiating with you how to make a connection to your particular  
service and program specific code to deal with your personal format for  
sending the events.

As an example, you can make a chat server that sends events, then make a  
web page that includes that chat server as an event-source. In fact,  
there's one we prepared earlier[1] ... and an article about event-source  
[2].

There have been several efforts to produce something like this - another  
that was originally developed by the SVG community was "REX" [3].

[1] http://oxzone.opera.com:8088/
[2] http://labs.opera.com/news/2006/09/01/
[3] http://www.w3.org/TR/rex/

> [6]: <http://esw.w3.org/topic/HTML/AddedElementEventsource> and
> <http://dev.w3.org/cvsweb/~checkout~/html5/spec/Overview.html? 
> rev=1.78#the-event-source>

cheers

Chaals

-- 
   Charles McCathieNevile, Opera Software: Standards Group
   hablo español  -  je parle français  -  jeg lærer norsk
chaals@opera.com   http://snapshot.opera.com - Kestrel (9.5α1)

Received on Thursday, 6 September 2007 05:12:36 UTC