Browse Prior Art Database

Mechanism for Programmatically Determining When Dynamic, Cached Data, Needs to be Refreshed Automatically on a Displayed Page

IP.com Disclosure Number: IPCOM000030812D
Original Publication Date: 2004-Aug-27
Included in the Prior Art Database: 2004-Aug-27
Document File: 2 page(s) / 34K

Publishing Venue

IBM

Abstract

Today, when a page is loaded many browsers, such as Internet Explorer, give you a way to configure your browser in such a manner as to check for newer versions of stored, i.e. cached, pages prior to a page being displayed. However, with the dynamic nature of many pages today there is no mechanism for a user to indicate when, or if at all, they'd like the page they are currently viewing to be refreshed with the latest data. The user can do this manually via a Refresh but some 'dynamic' and configurable method is needed for the user to indicate what they'd like to do. This removes the need for a button to be placed on the web page via the application, or for the client to have to hit Refresh to designate when the dynamic data should be refreshed. Ideally you'd like for the client's configuration to permit client control over when and how they wanted to see updated dynamic content displayed. This article provides a description of a possible mechanism to permit this.

This text was extracted from a PDF file.
At least one non-text object (such as an image or picture) has been suppressed.
This is the abbreviated version, containing approximately 52% of the total text.

Page 1 of 2

Mechanism for Programmatically Determining When Dynamic, Cached Data, Needs to be Refreshed Automatically on a Displayed Page

Today, when pages are displayed via a browser (see Internet Explorer example below), applet viewer, or other web based mechanism the client is typically provided with a set of configuration options to permit them to check for newer versions of stored, i.e. cached, pages prior to a page being displayed. However, once the page is displayed there is no mechanism for automatically refreshing the dynamic page content. As a result the user is forced to Refresh (either via the button or a user selectable button displayed on the page itself) the page to initiate the event to the server to update the data.

Some mechanism is required to allow the user to customize the display settings for pages containing dynamic content. The goal is to provide a mechanism for programmatic detection, via configuration setting(s), to determine if dynamic content needs to be updated, or not, on an already displayed page. This provides the user much more control over the data they see, prevents them from forcibly having to refresh the page and ensures that the data they are seeing is the most current. This also provides the application writer a more intuitive, and more dynamic, method of ensuring the user has the option of seeing the most recent data without placing some type of control mechanism on the page to permit the user to request a dynamic update in order to ensure they have the latest data.

New configuration settings could be added, an example of which is shown below, to give the client control over how, and when, to refresh dynamic content.

Check for updates to dynamic...