[7492] in www-talk@info.cern.ch

home help back first fref pref prev next nref lref last post

Re: Automatic Page Updates

daemon@ATHENA.MIT.EDU (Vinay Kumar)
Thu Feb 2 17:08:36 1995

Date: Thu, 2 Feb 1995 22:46:27 +0100
Errors-To: listmaster@www0.cern.ch
Reply-To: vinay@eit.COM
From: vinay@eit.COM (Vinay Kumar)
To: Multiple recipients of list <www-talk@www0.cern.ch>

Check out my "stock-ticker" application called "Media On
Demand" Server available at:
	http://www.eit.com/cgi-bin/mediaform

for a display/control of live audio/video media's. This has been
tested only using Mosaic (and not Netscape). You will also need
external viewer applications for audio/video. 

Enjoy,
--
  Vinay Kumar
vinay@eit.com
	"Bringing Real Time Network Media To The Desktop"

> From www-talk@www0.cern.ch Tue Jan 10 11:55:55 1995
> Date: Tue, 10 Jan 1995 20:44:53 +0100
> Reply-To: mogens@CS.Stanford.EDU
> Originator: www-talk@info.cern.ch
> Sender: www-talk@www0.cern.ch
> From: Christian Mogensen <mogens@CS.Stanford.EDU>
> To: Multiple recipients of list <www-talk@www0.cern.ch>
> Subject: Re: Automatic Page Updates 
> X-Listprocessor-Version: 6.0c -- ListProcessor by Anastasios Kotsikonas
> X-Comment: To sign off, send mail to listproc@info.cern.ch with body DEL WWW-TALK
> Content-Length: 983
> 
> >Is there any way in HTTP for a Server to automatically update a page
> >without requiring the user of the client to click on anything?
> 
> Currently no.  HTTP is connectionless, and that makes it hard to
> do things after a transaction is completed.
> 
> >An example use of this would be if a Client requests a stock price
> >page and keeps the page displayed.  Now suppose the stock price
> >changes.  Is there a way within HTTP for the Server to update the page
> >automatically without requiring the user to click on the reload option?
> 
> Another way to do this is to provide a stock-ticker application that
> is initialized by the web client when it receives application/x-stock-ticker
> data.  The browser forks off the special viewer which opens a separate
> communication channel to the server.
> 
> The previously noted use of Expires: xxx header is interesting - I don't 
> think it will work in the described manner until after a few revisions
> of browser software have passed...
> 
> Christian "web-head"
> 
> 
> 

home help back first fref pref prev next nref lref last post