Browse Prior Art Database

Method to cache information to enhance performance for computing context specific menus that are used to launch other applications

IP.com Disclosure Number: IPCOM000199277D
Publication Date: 2010-Aug-27
Document File: 3 page(s) / 36K

Publishing Venue

The IP.com Prior Art Database

Abstract

Disclosed is a method to cache information to enhance performance for computing context specific menus that are used to launch other applications

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 49% of the total text.

Page 1 of 3

Method to cache information to enhance performance for computing context specific menus that are used to launch other applications

Users of enterprise management applications typically use several management applications to manage their enterprise. Multiple applications need to be used since such applications focus on different problem spaces/aspects (enterprise storage management, element management for a device, etc) and also provide complimentary functions to perform various tasks. So, users need to constantly navigate from one application to another.

For purposes of the discussion when application A launches application B, application A is referred to as hosting application and application B is referred to as target application. Launch

point in a specific user interface refers to a widget on the user interface on which some entity can

be selected which has associated menus for launching another application. ex: a tab displaying several files. In this case the entities involved are files. Context refers to the characteristics of a specific resource that is related to an entity on one or more launch points.

The process to compute the context specific menus is processing intensive and computing the menus every time they need to be displayed is unnecessary since the context menus to be displayed and the parameters needed for the launch once a menu item is selected may not be changing for every instance such computation is needed. Computation is needed only when one of the following conditions occurs.
a) The configuration information provided by target applications changes,
b) Information pertaining to a resource in the hosting application changes such that the menus applicable to the context for the resource changes and/or the parameters to be used for the actual launch changes,
c)

New resource is discovered by the target application for which context menus need to be

computed

The performance of display of context menus and subsequent launch can be significantly improved if there is some logic that can be sophisticated enough to cache information and

perform computations only when neede

stale that could lead to incorrect menus been computer or incorrect launch to be performed.

The underlying concept for the idea is that multiple resource instances can share the exact same context which indirectly means that they can have same context specific menus and that re-computation is needed only when one of the conditions listed in the background information occurs.

The disclosure consists of the following:
1. A generic structure for caching in a scenario where there are resource instance specific characteristics and resource type specific characteristics. The structure consists of a set of tables that maintain some key mappings between resource instances to context instances, context instances and menus applicable to the context instance, resource instances and the parameters needed for URL formatting for launch entry points for that resource...