Client-side Data Culling
Original Publication Date: 2004-Jun-08
Included in the Prior Art Database: 2004-Jun-08
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 works well in splitting up data but can lead to latency as subsequent pages are requested from the server. These pages are often requested when the user clicks on a "previous" or "next" link or button. Also, a user often will toggle between a series of pages in order to analyze grouped data. As an example, imagine searching through a list of used cars on the cars.com website. A user might order a result set by price which spans several pages. The user will then toggle back and forth between two or more pages looking at cars that fall within their desired price range. Every time they "page" forward or backward to a subsequent page, they drive another request to the server and redundantly render table data. Futhermore, the server may also be redundantly pulling the data from a data store to regenerate the view.