Browse Prior Art Database

Representing subsets of remote data in a relative filter tree.

IP.com Disclosure Number: IPCOM000015895D
Original Publication Date: 2002-Apr-15
Included in the Prior Art Database: 2003-Jun-21
Document File: 3 page(s) / 47K

Publishing Venue

IBM

Abstract

The IBM Remote Systems Explorer Framework feature defines plug-in for the Eclipse project which provides a generic framework for accessing remote operating system artifacts such as file system objects, message queues, processes jobs and commands programs. This feature incorporates the concept of filtering remote information. End users can define a filter which is sent to the remote system and evaluated. The result is sent back to the Remote Systems Explorer end user and displayed in the graphical user interface. An eServer iSeries extension to the Remote Systems Explorer Framework feature allows filtering of both iSeries native file system objects and Integrated File System (IFS) objects. Filtering of remote file system objects is just a specific case of the more generic problem of displaying a subset of the information in a large model by applying some sort of filtering criteria over the model. This is often required when the model is so large that it cannot easily be viewed all at once. When modelling real world information in computer software, some internal representation needs to be used in order to preserve relationships in the information. A tree structure is frequently used to store the representation of a file system due to its hierarchical nature. In the case of the eServer iSeries extension to the Remote Systems Explorer Framework the entire model (a representation of the remote file system) is never loaded entirely into memory for the following reasons: The end user will typically only work with a small subset of the entire file system

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

Page 1 of 3

Representing subsets of remote data in a relative filter tree.

The IBM Remote Systems Explorer Framework feature defines plug-in for the Eclipse project which provides a generic framework for accessing remote operating system artifacts such as file system objects, message queues, processes / jobs and commands / programs. This feature incorporates the concept of filtering remote information. End users can define a filter which is sent to the remote system and evaluated. The result is sent back to the Remote Systems Explorer end user and displayed in the graphical user interface. An eServer iSeries extension to the Remote Systems Explorer Framework feature allows filtering of both iSeries native file system objects and Integrated File System (IFS) objects.

Filtering of remote file system objects is just a specific case of the more generic problem of displaying a subset of the information in a large model by applying some sort of filtering criteria over the model. This is often required when the model is so large that it cannot easily be viewed all at once. When modelling real world information in computer software, some internal representation needs to be used in order to preserve relationships in the information. A tree structure is frequently used to store the representation of a file system due to its hierarchical nature.

In the case of the eServer iSeries extension to the Remote Systems Explorer Framework the entire model (a representation of the remote file system) is never loaded entirely into memory for the following reasons:

The end user will typically only work with a small subset of the entire file system

The end user wait time and CPU / hard disk usage required to scan the entire file system and

build a corresponding in memory tree representation The end user wait time required to transmit an entire representation over the network from the

server to the client where Eclipse is running

Instead, the internal tree representation is built "on demand" as the end user requests information about the remote file system by specifying filters. If the end user requests information from the remote system by specifying a filter, the required information may already be contained in the local tree representation. The software response time and load on the remote server can be reduced if the software can recognize this situation and simply return the information from the local tree. Given a new filter defined by the end user and the internal tree representation of the remote file system, how does the software determine if the filter can be resolved locally?

This problem is the scope of this invention disclosure. The problem was solved by storing the filters that had been resolved on the remote system as nodes in the same tree which stores the internal representation of the remote information. This allows the tree to "remember" what sets of objects have already been retrieved.

This allows the software, running on the client, to determine...