CA2627718C - Method of selectively displaying data - Google Patents
Method of selectively displaying data Download PDFInfo
- Publication number
- CA2627718C CA2627718C CA2627718A CA2627718A CA2627718C CA 2627718 C CA2627718 C CA 2627718C CA 2627718 A CA2627718 A CA 2627718A CA 2627718 A CA2627718 A CA 2627718A CA 2627718 C CA2627718 C CA 2627718C
- Authority
- CA
- Canada
- Prior art keywords
- data items
- user
- data
- user front
- control information
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
- 238000000034 method Methods 0.000 title claims description 19
- 238000013500 data storage Methods 0.000 claims description 19
- 230000004044 response Effects 0.000 claims 6
- 238000012545 processing Methods 0.000 abstract description 10
- 230000006870 function Effects 0.000 description 7
- 230000008901 benefit Effects 0.000 description 3
- 238000010586 diagram Methods 0.000 description 2
- 239000003086 colorant Substances 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 238000012423 maintenance Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000001105 regulatory effect Effects 0.000 description 1
- 238000012546 transfer Methods 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/06—Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/24—Querying
- G06F16/245—Query processing
- G06F16/2455—Query execution
- G06F16/24552—Database cache management
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/10—Office automation; Time management
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q40/00—Finance; Insurance; Tax strategies; Processing of corporate or income taxes
- G06Q40/04—Trading; Exchange, e.g. stocks, commodities, derivatives or currency exchange
Abstract
To provide data to a user front end while conserving processor resources and network bandwidth, a front end driver operates between the user front end and data processing and storage devices. When users access databases from the user front end, the front end driver maintains virtual objects containing control information associated with the windows and data items visible at the user front end. The user front end need only maintain data corresponding to the visible data items, while the front end driver provides updated versions of the visible data items to the user front end. The updated data items may be provided at refresh intervals, independent of the rate at which the front end driver downloads data from the storage devices. Thus, the system provides access to all database data in a manner that appears to the user as real time, while conserving resources at the user front end.
Description
METHOD OF SELECTIVELY DISPLAYING DATA
BACKGROUND OF THE INVENTION
Field of the Invention The invention relates generally to data processing systems and, in particular, to systems that selectively display data.
Background Information In known systems that use data that are updated frequently remote users download, for example, database tables, and are provided in real time updated data for the various entries in the tables. Thus, a remote user who makes use of one or more rows io of a large database table must download the entire table to display the data in the rows of interest. In the example discussed below, a remote user who is a stock trader downloads a stock trading table that includes information for thousands of stocks in thousands of ta-ble rows. The thousands of rows are updated in real time, and thus, the remote user must utilize network bandwidth and front end memory that are sufficient to download, update is and maintain the stock trading table.
Many users require the information for only a relatively small number of stocks.
However, their front end systems must be capable of storing, maintaining and operating the entire stock trading table. Further, their networks must be capable of supplying up-dates to the various users in a sufficiently timely manner to promote trading.
Accord-20 ingly, many of the users are required to have systems that have capabilities that are well beyond what would be required if only the data of interest are made available.
What is needed is a system and method of operation that provides to respective users data of in-terest out of a larger collection of data in a manner that is sufficiently timely to promote real time use and updating of the data of interest.
BACKGROUND OF THE INVENTION
Field of the Invention The invention relates generally to data processing systems and, in particular, to systems that selectively display data.
Background Information In known systems that use data that are updated frequently remote users download, for example, database tables, and are provided in real time updated data for the various entries in the tables. Thus, a remote user who makes use of one or more rows io of a large database table must download the entire table to display the data in the rows of interest. In the example discussed below, a remote user who is a stock trader downloads a stock trading table that includes information for thousands of stocks in thousands of ta-ble rows. The thousands of rows are updated in real time, and thus, the remote user must utilize network bandwidth and front end memory that are sufficient to download, update is and maintain the stock trading table.
Many users require the information for only a relatively small number of stocks.
However, their front end systems must be capable of storing, maintaining and operating the entire stock trading table. Further, their networks must be capable of supplying up-dates to the various users in a sufficiently timely manner to promote trading.
Accord-20 ingly, many of the users are required to have systems that have capabilities that are well beyond what would be required if only the data of interest are made available.
What is needed is a system and method of operation that provides to respective users data of in-terest out of a larger collection of data in a manner that is sufficiently timely to promote real time use and updating of the data of interest.
2 SUMMARY OF THE INVENTION
In one aspect, the invention is a system and method of selectively providing data of interest to a user and making available to the user other data that may become of interest in a manner that promotes real time use of the data. The system includes a front end driver that operates between a user front end and data processing and storage devices. The front end driver controls the providing of data to the user front end based on what is visible to a user through the user front end at refresh times.
The front end driver also controls the updating of the data such that the visible data are updated during the refresh cycles, which are shorter than the times associated with refreshing, scrolling and resizing operations performed through the user front end display.
More specifically, the front end driver maintains virtual objects that contain control information for the windows and controls that are open at the user front end.
The control information associated with, for example, a database table, includes the top row then visible and the total number of rows visible in the given display, that is, within the dimensions of the associated window. The front end driver sends the data for the visible rows to the user front end and thereafter updates the data for the visible rows during refresh operations that occur at intervals that are fractions of a second. If the user changes the size of the respective windows or scrolls down a table, the system updates the associated control information and provides to the user front end the data for the newly visible rows at the next refresh cycle. The user front end thus need maintain only data that correspond to the visible rows, and yet the system has available to the user all of the data from the database table in a manner that appears to the user as real time, and given the timing of operations at the user front end is essentially real time.
According to another aspect of the invention, there is provided a method of providing to a user front end selected data items from a plurality of data items provided by a data storage device, the method comprising: associating a front end driver with the user front end, the front end driver being coupled in between the user front end and the one or more data storage devices over a network;
opening one or more windows on a display connected to the user front end, the one or more windows being associated with the plurality of data items; downloading the plurality of data items to the front end driver from the data storage device; selecting at the front end driver which data items of the plurality of data items are visible on the display at a given time in the one or more open windows at the user front end utilizing control information received from the user front end over the network; sending 2a the selected data items, determined to be visible for display at the user front end based on the control information, to the user front end from the front end driver; and displaying the selected data items in the one or more open windows at the user front end.
According to another aspect of the invention, there is provided a user front end for selectively displaying data provided over a network by a data storage device, the user front end comprising: a memory configured to store one or more data items, of a plurality of data items, that are visible on a display of the user front end at a given time; and a front end driver interface configured to:
communicate with a front end driver over the network, provide control information to the front end driver over the network, the control information utilized by the front end driver to determine selected data items of the plurality of data times that are visible on the display, and receive, over the network, the selected data items from the front end driver, wherein the front end driver downloads the plurality of data items from the data storage device over the network.
According to another aspect of the invention, there is provided a front end driver for providing over a network data items of a plurality of data items to one or more user front ends for selectively displaying data, the front end driver comprising: a data storage device interface configured to communicate with a data storage device and to receive the plurality of data items from the data storage device; a memory configured to store the plurality of data items; one or more user front end interfaces configured to communicate with the one or more user front ends over the network, the one or more user front end interfaces configured to receive, from the one or more user front ends, control information associated with one or more particular data items, of the plurality of data items, visible on a display of each user front ends at a given time; and a processor configured to utilize the received control information to determine that the one or more particular data items of the plurality of data items are visible on the display of each user front end at the given time and provide the selected one or more particular data items to the respective user front ends.
BRIEF DESCRIPTION OF THE DRAWINGS
The invention description below refers to the accompanying drawings, of which:
Fig. 1 is a functional block diagram of a system constructed in accordance with the invention;
In one aspect, the invention is a system and method of selectively providing data of interest to a user and making available to the user other data that may become of interest in a manner that promotes real time use of the data. The system includes a front end driver that operates between a user front end and data processing and storage devices. The front end driver controls the providing of data to the user front end based on what is visible to a user through the user front end at refresh times.
The front end driver also controls the updating of the data such that the visible data are updated during the refresh cycles, which are shorter than the times associated with refreshing, scrolling and resizing operations performed through the user front end display.
More specifically, the front end driver maintains virtual objects that contain control information for the windows and controls that are open at the user front end.
The control information associated with, for example, a database table, includes the top row then visible and the total number of rows visible in the given display, that is, within the dimensions of the associated window. The front end driver sends the data for the visible rows to the user front end and thereafter updates the data for the visible rows during refresh operations that occur at intervals that are fractions of a second. If the user changes the size of the respective windows or scrolls down a table, the system updates the associated control information and provides to the user front end the data for the newly visible rows at the next refresh cycle. The user front end thus need maintain only data that correspond to the visible rows, and yet the system has available to the user all of the data from the database table in a manner that appears to the user as real time, and given the timing of operations at the user front end is essentially real time.
According to another aspect of the invention, there is provided a method of providing to a user front end selected data items from a plurality of data items provided by a data storage device, the method comprising: associating a front end driver with the user front end, the front end driver being coupled in between the user front end and the one or more data storage devices over a network;
opening one or more windows on a display connected to the user front end, the one or more windows being associated with the plurality of data items; downloading the plurality of data items to the front end driver from the data storage device; selecting at the front end driver which data items of the plurality of data items are visible on the display at a given time in the one or more open windows at the user front end utilizing control information received from the user front end over the network; sending 2a the selected data items, determined to be visible for display at the user front end based on the control information, to the user front end from the front end driver; and displaying the selected data items in the one or more open windows at the user front end.
According to another aspect of the invention, there is provided a user front end for selectively displaying data provided over a network by a data storage device, the user front end comprising: a memory configured to store one or more data items, of a plurality of data items, that are visible on a display of the user front end at a given time; and a front end driver interface configured to:
communicate with a front end driver over the network, provide control information to the front end driver over the network, the control information utilized by the front end driver to determine selected data items of the plurality of data times that are visible on the display, and receive, over the network, the selected data items from the front end driver, wherein the front end driver downloads the plurality of data items from the data storage device over the network.
According to another aspect of the invention, there is provided a front end driver for providing over a network data items of a plurality of data items to one or more user front ends for selectively displaying data, the front end driver comprising: a data storage device interface configured to communicate with a data storage device and to receive the plurality of data items from the data storage device; a memory configured to store the plurality of data items; one or more user front end interfaces configured to communicate with the one or more user front ends over the network, the one or more user front end interfaces configured to receive, from the one or more user front ends, control information associated with one or more particular data items, of the plurality of data items, visible on a display of each user front ends at a given time; and a processor configured to utilize the received control information to determine that the one or more particular data items of the plurality of data items are visible on the display of each user front end at the given time and provide the selected one or more particular data items to the respective user front ends.
BRIEF DESCRIPTION OF THE DRAWINGS
The invention description below refers to the accompanying drawings, of which:
Fig. 1 is a functional block diagram of a system constructed in accordance with the invention;
3 Fig. 2 is a more detailed functional block diagram of a component of the system of Fig. 1; and Fig. 3 illustrates in views A and B operations of the component of Fig. 2.
DETAILED DESCRIPTION OF AN ILLUSTRATIVE
EMBODIMENT
A system 10 that provides data from data processing and storage devices 130 to users includes for each user a user front end 100 through which the user logs onto the system, views data, and so forth. A front end driver 120 communicates with the user front end and also with the data processing and storage devices 130, to provide user-requested data to the user front end for display. One example of such a system is a trading system that provides to the users market information, information relating to selected stocks, and so forth. The information is updated at the devices 130 frequently with information provided over a network (not shown), and the front end driver controls the updating of the displayed information at the user front end in a manner that appears to the user as real time.
A stock trading table may have thousands of rows to provide information for thousands of stocks, though a particular user may be interested in viewing the information relating to only a few of the stocks at any given time. As discussed in more detail below, the front end driver 120 operates to provide and update data that are displayed at the user's front end and essentially avoids providing or updating data that are not displayed. Further, the front end driver provides data and updates in a manner that to the user appears as if the data is available locally, in real time, such that when the user scrolls down the table, resizes the display of the table to include more rows, and so forth, the appropriate data are displayed.
This is in stark contrast to conventional subscriber systems, which provide all of the table data to the user's front end when the user opens the table (or even before opening the table) and thereafter broadcast updates such that the user front end locally updates all of the data. The front end driver of the current system thus saves network
DETAILED DESCRIPTION OF AN ILLUSTRATIVE
EMBODIMENT
A system 10 that provides data from data processing and storage devices 130 to users includes for each user a user front end 100 through which the user logs onto the system, views data, and so forth. A front end driver 120 communicates with the user front end and also with the data processing and storage devices 130, to provide user-requested data to the user front end for display. One example of such a system is a trading system that provides to the users market information, information relating to selected stocks, and so forth. The information is updated at the devices 130 frequently with information provided over a network (not shown), and the front end driver controls the updating of the displayed information at the user front end in a manner that appears to the user as real time.
A stock trading table may have thousands of rows to provide information for thousands of stocks, though a particular user may be interested in viewing the information relating to only a few of the stocks at any given time. As discussed in more detail below, the front end driver 120 operates to provide and update data that are displayed at the user's front end and essentially avoids providing or updating data that are not displayed. Further, the front end driver provides data and updates in a manner that to the user appears as if the data is available locally, in real time, such that when the user scrolls down the table, resizes the display of the table to include more rows, and so forth, the appropriate data are displayed.
This is in stark contrast to conventional subscriber systems, which provide all of the table data to the user's front end when the user opens the table (or even before opening the table) and thereafter broadcast updates such that the user front end locally updates all of the data. The front end driver of the current system thus saves network
4 resources and bandwidth and also frees memory resources at the user front end by providing at any given time only data and updates that correspond to the user's front end display.
We explain the system 10 in terms of opening tables to display data. The system s may be used with other types of data display, and is particularly adapted for use with data that are frequently updated. Thus, while the illustrative embodiment described below is directed to displaying particular entries, rows, and/or columns of a table, the system may be used to display any number of selected data items of a plurality of data items. For example, the selected data items may be particular entries of a table, particular elements to of a graphic, particular colors of a palette, or any other subset of a plurality of data items as would be apparent to those skilled in the art.
Referring now also to Figs. 2 and 3, when a user logs on to the system 10 through the user front end 100, the system opens in a display 110 a main window 102 that offers to the user various menus 103 and so forth to, for example, open tables to display data of ts interest. In the example, the menu may be used to open a stock trading table, a bond trading table and so forth.
At the same time, the front end driver 120 creates a corresponding virtual user front end 100v with a main window object 102v. When the user opens, through the menu 103, a window 104 for a stock trading table 105, the front end driver opens a 20 corresponding stock table window object 104v and a stock table object 105v. Similarly, when the user opens a second window 106 for a bond trading table 107, through the main window 102 or through the stock table window 104, the front end driver opens a second table window object 106v and a corresponding table object 107v, and so forth.
The user front end 100 provides to the table objects control information, such as, for example, first 25 table row displayed and number of rows displayed, and so forth. The front end driver then determines which rows of the respective tables are visible to the user through the user front end display.
The front end driver 120 communicates with the data processing and storage devices 130, and in a known manner downloads the data for the opened tables 105 and 30 107 to the associated virtual user front end, or more particularly, to the associated table window objects 104v and 106v, respectively. The front end driver then through the control information provided to the table objects 105v and 107v determines which table rows are visible in the display at the user front end. At selected refresh intervals, for example, fractions of a second, the front end driver provides to the user front end 100 the s data that correspond to the rows that are determined to be then visible in the display 110.
At a first refresh time after the table is opened, for example, the front end driver provides to the user front end the data for each of the visible or partially visible rows in the two opened tables.
As the data processing and storage devices 130 update data for the full tables io and 107, the updated data are provided to the front end driver 120. The front end driver then updates the tables and sets dirty flags 112 for the updated rows. The updated data are not provided to the user front end 100, however, until a next refresh cycle.
When a refresh timer 122 goes off, the front end driver 120 calls a Display Data function associated with the virtual user front end 100v and does the same for every other Is virtual user front end (not shown). The virtual user front end 100v Display Data function then calls, for each window object 104v, 106v open within it, a Window Display Data function that, in turn, calls respective Table Display Data functions for the table objects 105v, 107v open within the respective windows. Each Table Display Data function checks the rows of the associated full table that correspond to the rows that are visible in 20 the user front end, to determine if any of the rows have dirty flags 112 set. If one or more flags are set, the Table Display Data function calls a GetCellData function, which provides the data for the flagged rows to the user front end. At the end of the refresh operation, the front end driver resets the dirty flags 112.
As noted, the timing of the refresh intervals differ from the timing of the table 25 update intervals and the data transfer rates may vary as well. The table update interval timing may vary due, for example, to an amount of network traffic between the front end driver 120 and the storage devices 130, while the refresh interval may be regulated by the front end driver 120 to conform to the bandwidth and processing capacity of the user front end 100. Thus, during a table update interval large amounts of data may be 30 provided to the front end driver 120 at a high data rate through a connection specially suited to that purpose, while the selected data may be provided to the user front end 100 at a lower data rate through a more conventional connection within the user's network.
At the user front end 100 the data for the visible rows are maintained in a memory 101 and the data for the rows that are not then visible are discarded.
Accordingly, the s memory need only be large enough to maintain the maximum amount of data that can be displayed at a given time in the main window 102. The user front end then displays the data held in the memory 101 in the windows 104, 106.
When a user scrolls down a displayed table, for example, table 105, the user front end 100 sends updated control information to the front end driver 120, to inform the front io end driver of the new top row and the number of rows that are visible in the front end display. The front end driver then updates the control information in the associated table object, and sets dirty flags for the newly visible rows in the table that is contained in the corresponding window object. At a next refresh cycle, the front end driver provides to the user front end the data for any flagged rows, which include the newly visible rows Is and also any updated rows that are then still visible. As discussed, the refresh cycles occur at a rate that is selected to provide data to the user front end in what appears to the user to be real time. The data are thus provided at a rate that is faster than the scroll rate of the display, and there is no perceived delay at the user front end.
Similarly, when a user resizes a window to display more of a table, the front end 20 driver 120 updates the control information to reflect the new number of rows and the new top visible row and flags the new rows in the table of the corresponding window object.
The front end driver then provides data for flagged rows, that is, the newly visible rows as well as the updated rows that remain visible at the next refresh cycle. As discussed, the refresh operation provides the data in what appears to the user to be real time.
25 The user thus has available essentially at all times all of the data in the tables 105 and 107 and all of the updates to the data, while the user front end receives and stores only the data which at a given time is displayed to the user, and network resources and bandwidth are thus saved. As described, the updating of the information that is visible to the user is done at predetermined intervals, regardless of when the information is updated 30 in the database tables, again preserving network bandwidth and resources and providing an orderly, managed flow of data to the user front end. The updating, however, occurs at a rate that provides the user with the ability to resize and/or scroll down through, for example, a table, to view other rows in what appears to the user to be real time. Remote users are thus able to view data and perform operations based on that data, without having to download and maintain locally associated data that is not then of interest.
When a user has open a plurality of windows that are nested, the respective associated virtual window objects may contain control information that pertains to what data would be visible if each window were unobstructed. Accordingly, all of the data associated with what would be visible without the nesting may be sent to the user front io end 100. Alternatively, the system may send only the data associated with the portions of, in the example, the rows or columns that are actually visible within the respective windows through the nesting of the windows. Further, if some of the windows are instead "minimized" or entirely obscured, the system may but need not send the data for these windows. Thus, network bandwidth, processing resources, and memory 101 may is be conserved, as appropriate, even when a large number of windows are "open" but their data contents are not then visible at the user front end 100.
The front end driver 120 may service multiple user front ends 100. To accommodate multiple users opening the same database table, the virtual window objects 104v and 106v will contain "row-pointer tables" rather than the full database tables. The 20 row pointer tables contain rows that correspond to the rows of the associated database tables, and contain in the respective rows pointers to the corresponding rows of the full database table. Thus, a full database table is stored once at the front end driver and multiple pointer row tables are stored for the multiple users that are viewing the same table.
25 The row pointer table also includes, in the respective rows, flags that are set to indicate the rows that are visible at the user front end. The front end driver thus sets the flags based on the control information contained in the corresponding table object. The system uses the flags to determine which rows to check for updates, that is, which rows of the full database table to check for set dirty flags, during the refresh cycles.
The respective row-pointer table may also be re-arranged to correspond to the arrangement of the table at the user front end. For example, the row-pointer table may have the rows arranged in the alphabetical order of the entries in a given field of the full database table. The control information provided from the user front end corresponds to the re-arranged rows, and thus, the system readily accommodates the updating of the visible rows, scrolling down the rows, and so forth.
The system described above may be used with other control information from which the front end driver can determine the data of interest, and the system operations are thus not limited to database tables. Further, the data of interest may be selected columns of a database table or particular entries of selected table rows. The dirty flags may thus be set for the columns as well the rows. Alternatively, the system may send all column entries of interest for newly visible or updated rows.
The front end driver 120 downloads data from the data processing and storage devices 130 in a known manner in accordance with any privileges associated with the user.
For example, a given user may have rights to view particular market information, and thus, the tables downloaded for this user will contain only those entries that the user is entitled to view. While the users are generally remote users and thus benefit from acquiring and maintaining the relatively small amount of data that is displayed at the user front ends, the front end driver is typically located and/or operates to communicate with the devices 130 in a manner that allows fast downloading of, for example, data for the full table, and the updating of the full table data. The network bandwidth and resources are thus freed for other system operations.
It will be appreciated from the above-described embodiment that a system embodied in accordance with the invention facilitates the development and maintenance of user front ends because almost all of the business logic is implemented in the front end driver.
This provides a significant advantage in a system that includes hundreds of users but only one front end driver.
It can thus be seen in the advantages set forth above, including those made apparent from the preceding description, are efficiently attained with the invention.
Those skilled in the art will appreciate that various modifications may be made to the specific embodiment described herein without departing from the scope of the invention.
What is claimed is:
We explain the system 10 in terms of opening tables to display data. The system s may be used with other types of data display, and is particularly adapted for use with data that are frequently updated. Thus, while the illustrative embodiment described below is directed to displaying particular entries, rows, and/or columns of a table, the system may be used to display any number of selected data items of a plurality of data items. For example, the selected data items may be particular entries of a table, particular elements to of a graphic, particular colors of a palette, or any other subset of a plurality of data items as would be apparent to those skilled in the art.
Referring now also to Figs. 2 and 3, when a user logs on to the system 10 through the user front end 100, the system opens in a display 110 a main window 102 that offers to the user various menus 103 and so forth to, for example, open tables to display data of ts interest. In the example, the menu may be used to open a stock trading table, a bond trading table and so forth.
At the same time, the front end driver 120 creates a corresponding virtual user front end 100v with a main window object 102v. When the user opens, through the menu 103, a window 104 for a stock trading table 105, the front end driver opens a 20 corresponding stock table window object 104v and a stock table object 105v. Similarly, when the user opens a second window 106 for a bond trading table 107, through the main window 102 or through the stock table window 104, the front end driver opens a second table window object 106v and a corresponding table object 107v, and so forth.
The user front end 100 provides to the table objects control information, such as, for example, first 25 table row displayed and number of rows displayed, and so forth. The front end driver then determines which rows of the respective tables are visible to the user through the user front end display.
The front end driver 120 communicates with the data processing and storage devices 130, and in a known manner downloads the data for the opened tables 105 and 30 107 to the associated virtual user front end, or more particularly, to the associated table window objects 104v and 106v, respectively. The front end driver then through the control information provided to the table objects 105v and 107v determines which table rows are visible in the display at the user front end. At selected refresh intervals, for example, fractions of a second, the front end driver provides to the user front end 100 the s data that correspond to the rows that are determined to be then visible in the display 110.
At a first refresh time after the table is opened, for example, the front end driver provides to the user front end the data for each of the visible or partially visible rows in the two opened tables.
As the data processing and storage devices 130 update data for the full tables io and 107, the updated data are provided to the front end driver 120. The front end driver then updates the tables and sets dirty flags 112 for the updated rows. The updated data are not provided to the user front end 100, however, until a next refresh cycle.
When a refresh timer 122 goes off, the front end driver 120 calls a Display Data function associated with the virtual user front end 100v and does the same for every other Is virtual user front end (not shown). The virtual user front end 100v Display Data function then calls, for each window object 104v, 106v open within it, a Window Display Data function that, in turn, calls respective Table Display Data functions for the table objects 105v, 107v open within the respective windows. Each Table Display Data function checks the rows of the associated full table that correspond to the rows that are visible in 20 the user front end, to determine if any of the rows have dirty flags 112 set. If one or more flags are set, the Table Display Data function calls a GetCellData function, which provides the data for the flagged rows to the user front end. At the end of the refresh operation, the front end driver resets the dirty flags 112.
As noted, the timing of the refresh intervals differ from the timing of the table 25 update intervals and the data transfer rates may vary as well. The table update interval timing may vary due, for example, to an amount of network traffic between the front end driver 120 and the storage devices 130, while the refresh interval may be regulated by the front end driver 120 to conform to the bandwidth and processing capacity of the user front end 100. Thus, during a table update interval large amounts of data may be 30 provided to the front end driver 120 at a high data rate through a connection specially suited to that purpose, while the selected data may be provided to the user front end 100 at a lower data rate through a more conventional connection within the user's network.
At the user front end 100 the data for the visible rows are maintained in a memory 101 and the data for the rows that are not then visible are discarded.
Accordingly, the s memory need only be large enough to maintain the maximum amount of data that can be displayed at a given time in the main window 102. The user front end then displays the data held in the memory 101 in the windows 104, 106.
When a user scrolls down a displayed table, for example, table 105, the user front end 100 sends updated control information to the front end driver 120, to inform the front io end driver of the new top row and the number of rows that are visible in the front end display. The front end driver then updates the control information in the associated table object, and sets dirty flags for the newly visible rows in the table that is contained in the corresponding window object. At a next refresh cycle, the front end driver provides to the user front end the data for any flagged rows, which include the newly visible rows Is and also any updated rows that are then still visible. As discussed, the refresh cycles occur at a rate that is selected to provide data to the user front end in what appears to the user to be real time. The data are thus provided at a rate that is faster than the scroll rate of the display, and there is no perceived delay at the user front end.
Similarly, when a user resizes a window to display more of a table, the front end 20 driver 120 updates the control information to reflect the new number of rows and the new top visible row and flags the new rows in the table of the corresponding window object.
The front end driver then provides data for flagged rows, that is, the newly visible rows as well as the updated rows that remain visible at the next refresh cycle. As discussed, the refresh operation provides the data in what appears to the user to be real time.
25 The user thus has available essentially at all times all of the data in the tables 105 and 107 and all of the updates to the data, while the user front end receives and stores only the data which at a given time is displayed to the user, and network resources and bandwidth are thus saved. As described, the updating of the information that is visible to the user is done at predetermined intervals, regardless of when the information is updated 30 in the database tables, again preserving network bandwidth and resources and providing an orderly, managed flow of data to the user front end. The updating, however, occurs at a rate that provides the user with the ability to resize and/or scroll down through, for example, a table, to view other rows in what appears to the user to be real time. Remote users are thus able to view data and perform operations based on that data, without having to download and maintain locally associated data that is not then of interest.
When a user has open a plurality of windows that are nested, the respective associated virtual window objects may contain control information that pertains to what data would be visible if each window were unobstructed. Accordingly, all of the data associated with what would be visible without the nesting may be sent to the user front io end 100. Alternatively, the system may send only the data associated with the portions of, in the example, the rows or columns that are actually visible within the respective windows through the nesting of the windows. Further, if some of the windows are instead "minimized" or entirely obscured, the system may but need not send the data for these windows. Thus, network bandwidth, processing resources, and memory 101 may is be conserved, as appropriate, even when a large number of windows are "open" but their data contents are not then visible at the user front end 100.
The front end driver 120 may service multiple user front ends 100. To accommodate multiple users opening the same database table, the virtual window objects 104v and 106v will contain "row-pointer tables" rather than the full database tables. The 20 row pointer tables contain rows that correspond to the rows of the associated database tables, and contain in the respective rows pointers to the corresponding rows of the full database table. Thus, a full database table is stored once at the front end driver and multiple pointer row tables are stored for the multiple users that are viewing the same table.
25 The row pointer table also includes, in the respective rows, flags that are set to indicate the rows that are visible at the user front end. The front end driver thus sets the flags based on the control information contained in the corresponding table object. The system uses the flags to determine which rows to check for updates, that is, which rows of the full database table to check for set dirty flags, during the refresh cycles.
The respective row-pointer table may also be re-arranged to correspond to the arrangement of the table at the user front end. For example, the row-pointer table may have the rows arranged in the alphabetical order of the entries in a given field of the full database table. The control information provided from the user front end corresponds to the re-arranged rows, and thus, the system readily accommodates the updating of the visible rows, scrolling down the rows, and so forth.
The system described above may be used with other control information from which the front end driver can determine the data of interest, and the system operations are thus not limited to database tables. Further, the data of interest may be selected columns of a database table or particular entries of selected table rows. The dirty flags may thus be set for the columns as well the rows. Alternatively, the system may send all column entries of interest for newly visible or updated rows.
The front end driver 120 downloads data from the data processing and storage devices 130 in a known manner in accordance with any privileges associated with the user.
For example, a given user may have rights to view particular market information, and thus, the tables downloaded for this user will contain only those entries that the user is entitled to view. While the users are generally remote users and thus benefit from acquiring and maintaining the relatively small amount of data that is displayed at the user front ends, the front end driver is typically located and/or operates to communicate with the devices 130 in a manner that allows fast downloading of, for example, data for the full table, and the updating of the full table data. The network bandwidth and resources are thus freed for other system operations.
It will be appreciated from the above-described embodiment that a system embodied in accordance with the invention facilitates the development and maintenance of user front ends because almost all of the business logic is implemented in the front end driver.
This provides a significant advantage in a system that includes hundreds of users but only one front end driver.
It can thus be seen in the advantages set forth above, including those made apparent from the preceding description, are efficiently attained with the invention.
Those skilled in the art will appreciate that various modifications may be made to the specific embodiment described herein without departing from the scope of the invention.
What is claimed is:
Claims (33)
1. A method of providing to a user front end selected data items from a plurality of data items provided by a data storage device, the method comprising:
associating a front end driver with the user front end, the front end driver being coupled in between the user front end and the one or more data storage devices over a network;
opening one or more windows on a display connected to the user front end, the one or more windows being associated with the plurality of data items;
downloading the plurality of data items to the front end driver from the data storage device;
selecting at the front end driver which data items of the plurality of data items are visible on the display at a given time in the one or more open windows at the user front end utilizing control information received from the user front end over the network;
sending the selected data items, determined to be visible for display at the user front end based on the control information, to the user front end from the front end driver; and displaying the selected data items in the one or more open windows at the user front end.
associating a front end driver with the user front end, the front end driver being coupled in between the user front end and the one or more data storage devices over a network;
opening one or more windows on a display connected to the user front end, the one or more windows being associated with the plurality of data items;
downloading the plurality of data items to the front end driver from the data storage device;
selecting at the front end driver which data items of the plurality of data items are visible on the display at a given time in the one or more open windows at the user front end utilizing control information received from the user front end over the network;
sending the selected data items, determined to be visible for display at the user front end based on the control information, to the user front end from the front end driver; and displaying the selected data items in the one or more open windows at the user front end.
2. The method of claim 1 wherein the plurality of data items comprises a table of data, and selecting the data items includes determining which entries of the table are visible in the one or more open windows.
3. The method of claim 2 wherein the table of data comprises a stock trading table having information associated with at least one stock.
4. The method of claim 2 wherein determining which entries of the table are visible includes determining a number of rows of the table that are visible in the one or more open windows, and the control information identifying a first row of the number of rows for the one or more open windows.
5. The method of claim 1 wherein associating the front end driver with the user front end includes opening a virtual user front end at the front end driver, and storing, at the virtual user front end, one or more virtual objects associated with the one or more open windows, the virtual objects containing the control information.
6. The method of claim 5 further comprising:
opening a next window on the display connected to the user front end;
storing, at the virtual user front end, a next virtual window object corresponding to the next open window; and associating, with the next virtual window object, control information that specifies which particular data items are to be displayed in the next open window.
opening a next window on the display connected to the user front end;
storing, at the virtual user front end, a next virtual window object corresponding to the next open window; and associating, with the next virtual window object, control information that specifies which particular data items are to be displayed in the next open window.
7. The method of claim 6 further comprising:
opening a table within the window on the display connected to the user front end;
associating, with the virtual window object, a virtual table object corresponding to the open table; and associating, with the virtual table object, control information that specifies data items from that table that are to be displayed in the open window.
opening a table within the window on the display connected to the user front end;
associating, with the virtual window object, a virtual table object corresponding to the open table; and associating, with the virtual table object, control information that specifies data items from that table that are to be displayed in the open window.
8. The method of claim 1 wherein sending the selected data items to the user front end occurs at a refresh interval.
9. The method of claim 8 wherein the refresh interval is selected to provide data items to the user front end at a rate faster than a scroll rate of the display connected to the user front end.
10. The method of claim 9 wherein the sending the selected data items to the user front end further includes associating, at the front end driver, flags with respective selected data items that are updated at the front end driver, and sending the flagged data items to the user front end at a next refresh interval.
11. The method of claim 1 wherein selecting the data items includes selecting different data items in response to the one or more open windows being resized.
12. The method of claim 1 further comprising:
discarding, from the user front end, at least one data item of the selected data items in response to the at least one data item not being visible at the display at the user front end.
discarding, from the user front end, at least one data item of the selected data items in response to the at least one data item not being visible at the display at the user front end.
13. A user front end for selectively displaying data provided over a network by a data storage device, the user front end comprising:
a memory configured to store one or more data items, of a plurality of data items, that are visible on a display of the user front end at a given time;
and a front end driver interface configured to:
communicate with a front end driver over the network, provide control information to the front end driver over the network, the control information utilized by the front end driver to determine selected data items of the plurality of data times that are visible on the display, and receive, over the network, the selected data items from the front end driver, wherein the front end driver downloads the plurality of data items from the data storage device over the network.
a memory configured to store one or more data items, of a plurality of data items, that are visible on a display of the user front end at a given time;
and a front end driver interface configured to:
communicate with a front end driver over the network, provide control information to the front end driver over the network, the control information utilized by the front end driver to determine selected data items of the plurality of data times that are visible on the display, and receive, over the network, the selected data items from the front end driver, wherein the front end driver downloads the plurality of data items from the data storage device over the network.
14. The user front end of claim 13 wherein the plurality of data items include a table of data and wherein particular entries of the table of data include the selected data items.
15. The user front end of claim 14 wherein the table of data comprises a stock trading table having information associated with at least one stock.
16. The user front end of claim 14 wherein the particular entries include one or more of a group consisting of a number of rows of the table of data, and wherein the control information identifies the particular entries.
17. The user front end of claim 14 wherein the display is further configured to display the selected data items in a window and to provide the control information, to the front end driver, which associates the control information with a virtual object that corresponds to the window, the control information specifying the selected data items for display in the window.
18. The user front end of claim 13 wherein the display is configured to display the selected data items in a window and receive from the front end driver the selected data items at a refresh interval and in response to the control information being provided to the front end driver.
19. The user front end of claim 18 wherein the selected data items are determined in response to one or more of a group consisting of the window being resized and the window being scrolled.
20. The user front end of claim 13 wherein the display is configured to display a plurality of overlapping windows, and wherein the front end driver interface is further configured to provide control information, that corresponds to the selected data items for display in respective windows of the overlapping windows to the front end driver, the control information for association with virtual windows that correspond to the respective overlapping windows.
21. The user front end of claim 20 wherein the front end driver interface is further configured to receive from the front end driver only the selected data items that are visible at the user interface as determined using the control information.
22. The user front end of claim 13 wherein the front end driver interface is further configured to receive the selected data items from the front end driver at a refresh interval.
23. The user front end of claim 22 wherein the refresh interval is selected to provide the selected data items to the user front end at a rate faster than a scroll rate of the user interface.
24. The user front end of claim 13 wherein the front end driver interface is further configured to receive an updated data item from the front end driver, the updated data item associated with a flag in response to the front end driver receiving the updated data item from the data storage device.
25. A front end driver for providing over a network data items of a plurality of data items to one or more user front ends for selectively displaying data, the front end driver comprising:
a data storage device interface configured to communicate with a data storage device and to receive the plurality of data items from the data storage device;
a memory configured to store the plurality of data items;
one or more user front end interfaces configured to communicate with the one or more user front ends over the network, the one or more user front end interfaces configured to receive, from the one or more user front ends, control information associated with one or more particular data items, of the plurality of data items, visible on a display of each user front ends at a given time; and a processor configured to utilize the received control information to determine that the one or more particular data items of the plurality of data items are visible on the display of each user front end at the given time and provide the selected one or more particular data items to the respective user front ends.
a data storage device interface configured to communicate with a data storage device and to receive the plurality of data items from the data storage device;
a memory configured to store the plurality of data items;
one or more user front end interfaces configured to communicate with the one or more user front ends over the network, the one or more user front end interfaces configured to receive, from the one or more user front ends, control information associated with one or more particular data items, of the plurality of data items, visible on a display of each user front ends at a given time; and a processor configured to utilize the received control information to determine that the one or more particular data items of the plurality of data items are visible on the display of each user front end at the given time and provide the selected one or more particular data items to the respective user front ends.
26. The front end driver of claim 25 wherein the memory is further configured to store the control information associated with the one or more particular data items.
27. The front end driver of claim 25 wherein the processor is further configured to provide an updated data item to the respective user front ends at one or more refresh intervals and based on updated control information.
28. The front end driver of claim 27 wherein the data storage device interface is further configured to receive other data items from the data storage device at an update interval, and wherein the update interval differs from the one or more refresh intervals.
29. The front end driver of claim 26 wherein the memory is further configured to associate for the respective user front ends the one or more particular data items with one or more virtual objects.
30. The front end driver of claim 29 wherein the control information identifies the one or more particular data items of the virtual objects, and wherein the processor is further configured to provide the one or more particular data items in response to receiving the control information.
31. The front end driver of claim 30 wherein a table of data comprises the plurality of data items, and wherein the one or more particular data items include a number of rows of the table, and the control information specifies the number of rows.
32. The front end driver of claim 29 wherein the virtual objects contain row-pointer tables that include rows that correspond to the rows of the table of data and the respective rows of the row-pointer table contain pointers to the rows of the table of data, and flags that are set based on the control information to indicate the data table rows that are visible on the display at the respective user front ends.
33. The front end driver of claim 25, wherein the particular data items provided to a first user front end of the one or more user front ends are different than the particular data items provided to a second user front of the one or more user front ends.
Applications Claiming Priority (3)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| US72011905P | 2005-09-23 | 2005-09-23 | |
| US60/720,119 | 2005-09-23 | ||
| PCT/US2006/036979 WO2007038266A2 (en) | 2005-09-23 | 2006-09-22 | Method of selectively displaying data |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CA2627718A1 CA2627718A1 (en) | 2007-04-05 |
| CA2627718C true CA2627718C (en) | 2015-08-25 |
Family
ID=37801416
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CA2627718A Active CA2627718C (en) | 2005-09-23 | 2006-09-22 | Method of selectively displaying data |
Country Status (4)
| Country | Link |
|---|---|
| US (1) | US8073858B2 (en) |
| EP (1) | EP1927078A2 (en) |
| CA (1) | CA2627718C (en) |
| WO (1) | WO2007038266A2 (en) |
Families Citing this family (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US7979390B2 (en) * | 2006-10-27 | 2011-07-12 | Purdue Pharma L.P. | Software, systems, and methodologies for realignment of remote databases by a central database in support field representative territory assignments |
| US9483525B2 (en) * | 2007-04-30 | 2016-11-01 | Microsoft Technology Licensing, Llc | Reducing update conflicts when maintaining views |
| JP4342578B2 (en) * | 2007-07-24 | 2009-10-14 | 株式会社エヌ・ティ・ティ・ドコモ | Information processing apparatus and program |
| JP4750806B2 (en) * | 2008-01-07 | 2011-08-17 | 株式会社エヌ・ティ・ティ・ドコモ | Information processing apparatus and program |
| US10430298B2 (en) * | 2010-10-28 | 2019-10-01 | Microsoft Technology Licensing, Llc | Versatile in-memory database recovery using logical log records |
| US20130167072A1 (en) * | 2011-12-22 | 2013-06-27 | Sap Portals Israel Ltd. | Smart and Flexible Layout Context Manager |
| US20130162670A1 (en) * | 2011-12-23 | 2013-06-27 | Sap Ag | Dynamic card view |
| US9442640B2 (en) * | 2014-06-11 | 2016-09-13 | Google Inc. | Display mode based media player switching |
| US10572108B2 (en) * | 2017-07-20 | 2020-02-25 | Vmware, Inc. | Hierarchical inventory tree operation |
Family Cites Families (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US6408282B1 (en) | 1999-03-01 | 2002-06-18 | Wit Capital Corp. | System and method for conducting securities transactions over a computer network |
| US6839686B1 (en) * | 1999-03-29 | 2005-01-04 | Dlj Long Term Investment Corporation | Method and system for providing financial information and evaluating securities of a financial debt instrument |
| US7664695B2 (en) * | 2001-07-24 | 2010-02-16 | Stephen Cutler | Securities market and market maker activity tracking system and method |
| US20050187855A1 (en) | 2004-02-20 | 2005-08-25 | Brennan David P. | Method for analyzing trade data |
| US8296646B2 (en) * | 2005-02-02 | 2012-10-23 | International Business Machines Corporation | Focusing on areas of the display of tabular data through hierarchical collapsing and expanding of cell areas |
-
2006
- 2006-09-22 CA CA2627718A patent/CA2627718C/en active Active
- 2006-09-22 WO PCT/US2006/036979 patent/WO2007038266A2/en active Application Filing
- 2006-09-22 EP EP06825071A patent/EP1927078A2/en not_active Withdrawn
- 2006-09-22 US US11/525,506 patent/US8073858B2/en not_active Expired - Fee Related
Also Published As
| Publication number | Publication date |
|---|---|
| WO2007038266A3 (en) | 2007-05-18 |
| WO2007038266A2 (en) | 2007-04-05 |
| CA2627718A1 (en) | 2007-04-05 |
| EP1927078A2 (en) | 2008-06-04 |
| US20070219935A1 (en) | 2007-09-20 |
| US8073858B2 (en) | 2011-12-06 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CA2627718C (en) | Method of selectively displaying data | |
| AU2005202717B2 (en) | User interface for providing task management and calendar information | |
| US6421071B1 (en) | Synchronous scrolling of time stamped log files | |
| US8078985B2 (en) | Scrolling of ordered series with item highlighting indicating relevance | |
| US6593949B1 (en) | Smart column for contact information on palm-sized computing devices and method and apparatus for displaying the same | |
| US20070174432A1 (en) | Apparatus for and method of displaying communication log using GUI image | |
| US20080313567A1 (en) | System and Method for Providing Dynamic Prioritization and Importance Filtering of Computer Desktop Icons and Program Menu Items | |
| US20060224992A1 (en) | Graphical user interface management | |
| US20120124497A1 (en) | Method and apparatus for data virtualization and display | |
| CN104021016B (en) | Method and browser for loading browser plug-in icons | |
| CN105573761A (en) | Method for mobile terminal to display application program on the basis of user habits, and mobile terminal | |
| CN105589932A (en) | Page configuration method and apparatus | |
| US20050108277A1 (en) | Persistent state database for operating system services | |
| JP3384517B2 (en) | Electronic cash register | |
| CN111857453A (en) | Function interface display method, computer equipment and storage medium | |
| US20230350882A1 (en) | Automatically generated graphical user interface application with dynamic user interface segment elements | |
| CN107301182A (en) | A kind of method and apparatus for the webpage for showing embedded picture | |
| US5793860A (en) | Method and arrangement for controlling performance features of an exchange | |
| US20040012615A1 (en) | Mobile communication terminal capable of editing a screen image on a display and method thereof | |
| US20040225969A1 (en) | Hand-portable electronic device with symbolic calendar application | |
| CN110264282A (en) | Advertisement orients put-on method, device and computer readable storage medium | |
| CN106375190B (en) | instant messaging software interface splitting and merging display method and system | |
| US9860344B2 (en) | Self-management of local resources allocated remotely | |
| US20050132331A1 (en) | Assisting in configuring network devices | |
| EP4260208A1 (en) | Determination of result data for small multiples based on subsets of a data set |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| EEER | Examination request |