Browse Prior Art Database

Client-side Data Culling

IP.com Disclosure Number: IPCOM000028940D
Original Publication Date: 2004-Jun-08
Included in the Prior Art Database: 2004-Jun-08
Document File: 1 page(s) / 28K

Publishing Venue

IBM

Abstract

The problem realized is that often large amounts of data are displayed in table format as part of markup served to clients via Internet. Futhermore, due to the amount of data and small display real-estate of monitors and mobile display units, this table data is "paged", broken into a series of subsequent pages.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 67% of the total text.

Page 1 of 1

Client-side Data Culling

This article proposes to cache (store on client) and cull (remove from client) paged data displayed in table format in order to expidite and improve the user experience.

Initial Data Request

When a table of data is displayed, it will be broken up into a series of pages consisting of between 0 .. n result set rows. In performing an initial request for the first page of data, this invention proposes the following flow:

1. Request initial page of table data from server
2. Render table data in appropriate markup
3. Drive discrete request to server for subsequent page of data
4. Cache returned data on client in "next cache"

Subsequent Data Request

When the user then requests the next page, it already exists on the client. The following flow would apply:

1. Check "next cache" for data
2. If not present, drive full request
3. If present, drive simple request to server to check data validity (might be invalid due to manipulation of data on server, session timeout, etc.)
4. If data is not valid, drive full request
5. If data is valid, move previous table data (current page) to "previous cache"
4. Update visible table rows with data from "next cache"
5. Drive discrete request to server for subsequent page of data

The benefit of this flow is that a large percentage of the time, the user will be presented with a subsequent page of data, discretely and immediately. Futhermore, in this likely case, the entire document did not refresh, thus improving the user's...