Browse Prior Art Database

Method for dynamic pre-caching remote data for UI panels

IP.com Disclosure Number: IPCOM000171652D
Original Publication Date: 2008-Jun-16
Included in the Prior Art Database: 2008-Jun-16
Document File: 4 page(s) / 48K

Publishing Venue

IBM

Abstract

Pre-caching the remote data associated with UI panels for logged in users is the main idea of the invention. The method is, 1, Find out which data should be retrieved from remote/slow repository. 2, When a user logs in to the system, get user's profile including role, id etc. 3, The user will use a function of the system, for example taking vacation applying process, the user will access several panels to go though the process. 4, For those potential visited panels, we can know all the associated items. 5, Based on the relationship among items on the panel, local database and remote data repository, we can figure out which remote data will be potentially used for the current logged in user. 6, System synchronizes those remote data with local repository to cache them. 7, The system will response quickly since it doesn’t need to fetch data remotely, all the data has already been cached locally.

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 4

Method for dynamic pre-caching remote data for UI panels

Take vacation applying process as example, the apply process contains several steps:
1) First panel - "histrionic records panel": View all vacation history records, and click "next" button.
2) Second panel - "vacation type selection panel": View and select one vacation type, e.g., optional days, annual leave etc. And click "next" button.
3) Third panel - "applying days panel": Get the number of remaining days, fill out the apply form and click "next".
4) Forth panel - "approver selection panel": Select manager or team lead, and then submit.

For this process, vacation information is retrieved from remote HR database, and user's manager/team lead information is retrieved from centralized user repository - a LDAP server.

If use the new method, the system should first figure out, for current user and process, what kind of remote data will be potentially used. And Pre-cache them with some certain strategies.

The system cab pre-define some panels as "root" panels.
1) Generate a "tree" model with a certain level of sub-nodes under the root panel.

The root panel can be the entry point panel of "vacation applying process" or one step in the process, or even take every step in the "vacation applying process" as the root panel.

After the root panel is determined, from this panel, the user can go to several other panels - those are the child nodes of root. And for those child panels, they can also navigate to other panels, so they can have their children too.

It looks like,

1

Page 2 of 4

For each node in the tree, it will display/use (maybe in backend layers) several items. Some attributes of the item may come from data types in remote repository. For example, the panel displays some historic vacation applying records, and for each record, the attribute "Employee Code" comes from remote user LDAP repository and the attribute "Total Days" is from remote HR database. For other attributes, like "Process Status", is from the local database maintained by the system itself.

2

[This page contains 15 pictures or other non-text objects]

Page 3 of 4

So, if the user accesses the root panel, the system can know that which remote data might be used later, based on some already known information like the profile of the user.
2) Pre-cache the data with strategies.

Since we know the potential used remote data for the current root panel, we can take some strategies from se...