Re: Automatic Refresh

Matthew,

here's roughly what I'd suggest, which expands on your idea:

- have a standard link "refresh data" that reloads the page as normal
- use javascript to write out another link "automatic refresh"
- this link triggers a javascript function that sets a cookie
- if the cookie is set, do a reload via javascript (not META) after a
set timeout period
- if the cookie is set, the link that's written out is changed to "stop
automatic refresh"
which unsets the cookie

Patrick
___________________________________________________________________________
re·dux (adj.): brought back; returned. used postpositively. [latin : re-,
re- + dux, leader; see duke.]
art and photography: http://redux.deviantart.com |
http://www.daprints.com/affiliates/photographia/
www.photographia.co.uk | http://www.splintered.co.uk/

----- Original Message ----- 
From: "Matthew Smith" <matt@kbc.net.au>
To: "WAI Interest Group" <w3c-wai-ig@w3.org>
Sent: Saturday, July 03, 2004 11:29 PM
Subject: Automatic Refresh


>
> Hi All
>
> I am working on an application that creates an XHTML page from data
acquired
> from a network of temperature sensors.
>
> As this data is "live", it needs to be refreshed on a regular basis.  I
have a
> mechanism that creates a refresh meta element so that the page will update
a few
> seconds after ever poll of the sensors.
>
> To make this accessible, would it be a simple case of starting off with no
> refresh (refresh element not included in page header) and having a link
> "automatic refresh" to start the cycle?  One would obviously have a "stop
> automatic refresh" control for when the cycle is running.
>
> If this is sound, an application like this could make all sorts
instrumentation
> accessible.
>
> Cheers
>
> M
>
> -- 
> Matthew Smith
> Kadina Business Consultancy
> South Australia
>
>
>
>

Received on Saturday, 3 July 2004 23:01:11 UTC