Web Browser Dataset Rendering via Server-Side Pagination
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Web browsers have limited memory capacity, making it difficult for users to access and manage large datasets, such as those used by property management companies, as the number of records can easily overflow the memory, restricting the ability to retrieve specific records efficiently.
Innovation Solution
A method and system for rendering subsets of ordered records on a web browser, which involves receiving inputs for ordering, indexing, and memory size, ordering the records, determining subsets to render, and transmitting these subsets for display, while utilizing caching to optimize memory usage and improve data access.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Quantity of substance
If users transfer large datasets to service providers' servers, then data management capability is improved, but web browser memory is exceeded making record access difficult
Solution Approach 1:
The patent divides the large dataset into multiple pages, each containing a subset of records that fits within web browser memory constraints. The system retrieves and displays one page at a time based on user navigation, preventing memory overflow while enabling access to large datasets through iterative page loading.
Solution Approach 2:
The system performs preliminary sorting and filtering operations on the server side before transmitting data to the client. By pre-processing the dataset to organize records according to user-specified criteria (such as sorting by property address or filtering by rental amount), the system reduces the amount of data that needs to be transferred and displayed, optimizing browser memory usage.
2Loss of energy
If web browsers store limited records in memory, then memory usage is controlled, but the ability to retrieve specific records from large datasets is restricted
Solution Approach 1:
The patent introduces a server as an intermediary between the large dataset and the web browser. The server acts as a mediator that performs sorting, filtering, and pagination operations, then transmits only the necessary subset of records to the browser. This intermediary approach allows efficient data retrieval without requiring the browser to handle the entire dataset.
Solution Approach 2:
The system performs preliminary sorting and filtering operations on the server side before transmitting data to the client. By pre-processing the dataset to organize records according to user-specified criteria (such as sorting by property address or filtering by rental amount), the system reduces the amount of data that needs to be transferred and displayed, optimizing browser memory usage.
3Measurement precision
If users access records for specific properties meeting certain criteria, then targeted data retrieval is improved, but the number of matching records may overflow browser memory
Solution Approach 1:
The patent divides the filtered results into paginated subsets, where each page contains a manageable number of records that fit within browser memory. Even when filtering returns many matching records (e.g., thousands of properties meeting certain criteria), the system displays them in controlled pages, allowing users to navigate through results without overwhelming the browser.
Solution Approach 2:
The system retrieves slightly more records than immediately visible on screen (including navigation buffers and adjacent pages) to enable smooth user interaction, but keeps the total transmitted data within memory constraints. This partial retrieval approach balances the need for targeted record access with browser memory limitations.
Data Source
AI summary
Systems and methods for sorting, grouping, and rendering subsets of large datasets over a network are described. Records may be sorted according to a user input, and the system may identify the subset of records that would be displayed on a client. The system may render for display only the identified records. Additionally, the system may render and cache records proximate to the identified records. Further, the system may perform searches upon the records and use the search results to further find results for a refined search.


