US 6,604,103 B1Grant
System and method for information retrieval employing a preloading procedure
Issue Date:2003-08-05
•5 Claims
•43 Drawing Sheets
Abstract
A document retrieval system having improved response time. During the time the user spends viewing the displayed information, other information that the user is likely to read or study later is preloaded into memory. If the user later requests the preloaded information, it can be written to the display very quickly. As a result, the user's request to view new information can be serviced quickly.
Metadata
Inventor
- Mark A. Wolfe
Application Information
Application Number:US 09/974,242
Filing Date:2001-10-09
Priority Date:1994-09-02
Art Unit:7
Classifications
IPC:
G06F 1730
Field of Search:
707 5707 107071027071041709201709202709218709203715501715513
Patent Drawings (43 sheets)
Description
[0002] This application is a continuation of application Ser. No. 09/620,651, filed Jul. 20, 2000, which is a continuation of Ser. No. 09/083,382, filed May 22, 1998, now abn. which is a continuation-in-part of Ser. No. 08/918,912, filed Aug. 27, 1997, now U.S. Pat. No. 5,946,682, issued Aug. 31, 1999, which is a continuation of Ser. No. 08/474,921, filed Jun. 7, 1995, now U.S. Pat. No. 5,715,445, issued Feb. 3, 1998, which is a continuation of Ser. No. 08/300,343, filed Sep. 2, 1994, now abandoned. This application also claims the benefit of provisional application Ser. No. 60/047,554, filed May 22, 1997. All of these applications are hereby fully incorporated by reference.
Field of the Invention
[0003] The present invention relates to a system for retrieving information from a database. More specifically, the present invention improves a system's response time so that a user's request to view new information is serviced quickly.
Background and Summary
[0004] The recent proliferation of electronic text and multimedia databases has placed at society's fingertips a wealth of information and knowledge. Typically, a computer is employed that locates and retrieves information from the database in response to a user's input. The requested information is then displayed on the computer's monitor. Modem database systems permit efficient, comprehensive, and convenient access to an infinite variety of documents, publications, periodicals, and newspapers. Yet retrieving information from databases is often slow. Sometimes, this is caused by bandwidth limitations, such as when information is retrieved from remotely-located databases over an ordinary telephone line, a very narrow bottleneck. In other cases, slow retrieval is caused by a relatively slow local mass storage device (e.g., a CD-ROM drive).
[0005] There exists a compelling need for a database system that has a quicker response time so that information is displayed very soon after the user requests it. This need can be satisfied by effectively utilizing the time the user spends studying information on the display screen. In a database system or document retrieval system in one embodiment of the present invention, information that the user is likely to eventually request is preloaded into memory while the user is viewing other information. In some embodiments, the present invention takes advantage of the fact that it is possible to accurately predict the information that the user will eventually request be shown on the display. Some embodiments of the present invention also take advantage of the fact that the time that the user spends viewing displayed information is often sufficient to advantageously preload a substantial amount of information.
[0006] With these and other objects, advantages, and features of the invention that may become hereinafter apparent, the nature of the invention may be more clearly understood by reference to the following detailed description of the invention, the appended claims, and to the several drawings herein.
Brief Description of the Drawings
[0007] FIG. 1ais a block diagram of a general purpose computer.
[0008] FIG. 1bis a diagram of multiple computers connected together to form a network of computers and/or networks.
[0009] FIGS. 1c, 1d, and 1gare diagrams illustrating various procedures for installing and executing software.
[0010] FIGS. 1eand 1fare flow charts illustrating procedures for installing and executing software.
[0011] FIG. 2 is a representation of four search documents and three related documents.
[0012] FIG. 3 is a representation of four search documents and three related documents with a display
[0013] view and one anticipated view designated.
[0014] FIGS. 4(a) and 4(b) are each a representation of four search documents and three related documents showing a display view and four anticipated views.
[0015] FIGS. 5(a) and 5(b) are each a representation of four search documents and three related documents showing various term views.
[0016] FIG. 6 is a representation of four search documents and three related documents showing various subdocument views.
[0017] FIG. 7 shows seven documents ordered according to four different ordering characteristics.
[0018] FIGS. 8, 9, and 10 are flowcharts illustrating alternate embodiments of the present invention.
[0019] FIG. 11 is a diagram of the relationships between six statically-related documents.
[0020] FIG. 12 is a representation of a video display screen for a computer such as that of FIG. 1a.
[0021] FIGS. 13a, 13b, 13c, 13d, and 13eare flow charts illustrating the operation of embodiments of the present invention.
[0022] FIG. 14 is a chart illustrating one example of the type of profile information that may be provided in connection with a given document.
[0023] FIG. 15 is a flow chart illustrating how profile information can be used in an embodiment of the present invention.
[0024] FIG. 16 is a flow chart of the operation of a system in one embodiment of the present invention where a plurality of documents are preloaded in separate threads of execution.
[0025] FIGS. 17ato 17fare representations of a video display screen illustrating various features and embodiments of the present invention.
[0026] FIGS. 18aand 18bare flow charts illustrating the operation of various embodiments of the invention.
[0027] FIG. 19 is a flow chart illustrating how an embodiment of the present invention can effectively operate in a fee-based environment.
[0028] FIGS. 20a, 20b, and 20care flow charts of the operation of embodiments of the present invention illustrating how server demands can be reduced in some circumstances.
[0029] FIG. 21 is a flow chart that illustrates the operation of a computer program illustrating some aspects of the present invention.
[0030] FIG. 22 is a flow chart that illustrates the use of an embedded program in connection with the present invention.
[0031] FIG. 23 is a network diagram illustrating an alternate method of preloading information on a network.
Detailed Description
[0032] FIG. 1ais a block diagram of a general purpose computer 102 that can be used to implement the present invention. The computer 102 has a central processing unit (CPU) 104, memory 113, and input/output (i/o) circuitry 112. The CPU 104 is connected to the memory 113 and the i/o circuitry. 112. The i/o circuitry permits the CPU 104 to access various peripheral devices, such as the display or monitor 108, local storage 106, and input device(s) 110. The input device(s) 110 may include a keyboard, mouse, pen, voice-recognition circuitry and/or software, or any other input device. Some type of secondary or mass storage 106 is generally used, and could be, for example, a hard disk or optical drive. The storage 106 can also be eliminated by providing a sufficient amount of memory 113. Either the storage 106 or the memory 113 could act as a program storage medium that holds instructions or source code. The i/o circuitry 112 is also connected to a network 114, thereby connecting the computer 102 to other computers or devices.
[0033] FIG. 1bis a representation of multiple computers (251, 252, 253, 254, 255, 256, and 257) connected together to form a network of computers and/or networks. Computers 251, 252, and 256 are shown connected to wide area network (WAN) 263, whereas computers 253, 254, 255, and 257 are shown interconnected by local area network (LAN) 261. The LAN 261 is connected to the WAN 263 by connection 262. Various network resources, such as databases of documents or other objects, are stored on one or more the computers shown in FIG. 1b.
[0034] In a networked environment, such as that of FIG. 1b, there are numerous ways in which software can be installed, distributed, and/or executed on the various computers on the network. FIG. 1cillustrates a conventional way in which desktop software is installed and executed. In FIG. 1c, a computer program 1003 is installed at the computer 1001 through some type of installation program typically started by the user of the computer 1001, and executed on the computer 1001. During installation, the program 1003 may need to be configured at the computer 1001 for use with the network in order to enable access to other computers on the network (e.g., 1002 and 1012). After installation, the computer program 1003 resides and executes at the computer 1001, and is persistent. When the computer 1001 is shut down or restarted, the program continues to be stored at the client on non-volatile storage media. Upon restarting the computer 1001, the program 1003 is available for use without reinstallation.
[0035] FIG. 1dshows a different embodiment. When the network-connected computer 1001 connects to or downloads an object stored on the remote computer 1002 over the network, a program 1005 embedded within the downloaded document or object is installed on the computer 1001 and is executed on the computer 1001. FIG. 1eis a flow chart that illustrates one possible installation procedure that is carried out when the computer 1001 accesses the program 1005.
[0036] The computer 1001 identifies at 1020 one or more programs embedded within the accessed object. The client computer then determines whether each embedded program has been installed previously on the computer 1001. This can be done by searching the computer's storage or system registry for the program or for the program's identifying characteristics. In Microsoft's ActiveX/COM architecture, for example, this is done by searching the registry for an instance of the program's globally unique identifier (GUID) in the system registry.
[0037] If the embedded program has been installed on the client computer, the previously installed program is retrieved from local storage at 1030, and executed at 1028. However, if the program has not been already installed on the client computer, it is retrieved over the network (1023), and installed on the client computer. The installation process will typically involve updating a system registry or other persistent storage with identifying information on the computer 1001.
[0038] Preferably, the program is installed at 1024 such that it need not be downloaded again over the network when it is encountered embedded within another object. For example, if the computer 1001 were to access an object on computer 1012 that had program 1005 embedded within it, the program 1005 would not need to be installed again because it has already been installed when computer 1002 was accessed.
[0039] FIG. 1fis flow chart illustrating a different embodiment of the present invention. In this system, when the computer 1001 encounters an object on computer 1002, it identifies at 1040 each program embedded within the object. It then retrieves one or more programs over the network, and then installs them at the client computer 1001, but without the use of a persistent storage mechanism. Thus, although the program is executed on the client computer 1001, the embedded program must be downloaded each time it is encountered because no persistent storage mechanism is used. This type of installation procedure may be more secure, and has been used in some of the early Java implementations.
[0040] A system in which software is downloaded over the network, perhaps from an untrusted server, has significant security risks associated with it, and for this reason, security restrictions may be placed on computer programs downloaded from the network. Thus, a downloaded computer program may be unable access some of the resources of a client computer or of the network generally. In some embodiments, however, a downloaded program may be tested for authenticity and safety through a code signing procedure, or through a code verifying procedure. If such a program passes such authenticity tests, it may be given more complete access to system or network resources.
[0041] In yet another embodiment, shown in FIG. 1g, the network-connected computer 1001 connects to the remote computer 1002 over the network, but the program 1021 executes on the remote computer 1002. Display information and/or instructions are sent from the remote computer 1002 to the computer 1001, and this information and/or instructions are interpreted by a terminal program or a thin client program 1023, which updates the display. Input device events (e.g., mouse clicks and keyboard events) caused by the user at the computer 1001 are sent to the remote computer 1002 so as to appropriately alter the execution of the program 1021 executing at the remote computer. In some implementations, it appears to the user of computer 1001 that the program 1021 is executing on computer 1001, even though the program 1021 is actually executing on the computer 1002. This scenario, or one similar to it, is employed by some of the thin-client computing environments, such as Citrix Corporation's WinFrame solution, or Microsoft's forthcoming Hydra initiative.
[0042] Each of the described techniques for installation and/or use of software can be implemented in connection with the present invention. For example, software used for carrying out one or more embodiments of the present invention may be installed and executed in accordance with the techniques described above.
[0043] In FIG. 2, four documents that might correspond to search documents found as a result of a query are shown. The query may be formulated to find all the documents in a given database that include the phrase “Hadley v. Baxendale.” Each X in the search documents 100A, 200A, 300A, and 400A represents an occurrence of the phrase “Hadley v. Baxendale.” As can be seen, the phrase “Hadley v. Baxendale” can be found in search document 100A at two separate locations. Document 200A has six occurrences, and search document 300A has three. Search document 400A has one occurrence—the title of search document 400A is “Hadley v. Baxendale.”
[0044] There are also “related documents” (500A, 600A, and 700A) shown in FIG. 2. A related document is a document that is somehow explicitly associated, linked, or otherwise connected to one of the search documents. For example, if search document 100A is, a judicial opinion, a related document might be a subsequent opinion in the same case (e.g., an decision on appeal). Other related documents might be an opinion or scholarly article that cites or discusses search document 100A, or a list of judicial opinions that cite the search document. Any document that is usefully associated with the search document can be considered a related document. Often the related document does not satisfy the query, so it is usually not one of the search documents. In some circumstances, however, the related document might satisfy the query, so it can be a search document.
[0045] Related documents may also be related only to a particular view within a search document. For example, a search document that is a judicial opinion may have numerous other judicial opinions cited in the text of the opinion. These cited opinions may be “related documents,” but often they relate only to a particular view within the document. Depending on the implementation of the database system, they might not be considered to be “related” to the search document as a whole. Thus, they are available as related documents only when the corresponding cite is within the currently displayed view. In such an implementation, the related documents are dependent on the view shown on the monitor at any given time.
[0046] FIG. 3 shows the representation of the four search documents that satisfy the user's query. The search documents are ordered by an ordering characteristic, such as the date of publication. Other ordering characteristics can be used as appropriate for a given situation (e.g., number of query-terms in a document, statistical relevance of the documents, type of document, etc.). Any ordering characteristic that permits the search documents to be distinguished from one another can be appropriate. In the example of FIG. 3, search document 100A is the first search document according to the ordering characteristic, and view 101A (shaded) in search document 100A is the display view shown on the monitor. (The view shown on the monitor at any given time is the “display view.”) Once view 101A is displayed on the monitor, the user reads, studies or otherwise observes the displayed information. When the user wishes to change the display view, he or she uses an input device to cause the system to display either (a) a different view in the search document 100A, or (b) a view from one of the other documents 200A, 300A, 400A, 500A, 600A, or 700A.
[0047] The user uses one or more input devices to request particular views. For example, an input device might be a keyboard that includes a “next page” key and a “next document” key. The “next page” key requests the next successive view (view 102A) within the document currently being viewed (document 100A). The “next document” view requests the first view (view 201A) of the next successive search document according to the ordering characteristic (document 200A). Many database systems have “next page” and “next document” commands or keys (e.g., Westlaw, LEXlS/NEXIS, and West Publishing Company's CD-ROM products), as well as others (e.g., “previous document,” “previous page”). Westlaw also permits a user to request a particular search document or “page” by typing a command. For example, to view search document three (300A), the user types “r3”;, to request page 2 (i.e., view 2) within the currently displayed document, the user types “p2.” And in some systems, multiple commands can be executed together by separating them with a semicolon, so page two from document three (view 302A) can be requested with a single command: “r3;p2.”
[0048] In the systems of the prior art, when the database system receives the command to display a different view, the requested view must be loaded from the database before it can be displayed on the monitor or display. Since retrieving information from the database is time-consuming, this loading process is undesirably slow. But in a system employing the present invention, the time required to respond to the user's request for a different view (the “requested view”) is reduced by taking advantage of the fact that it is often possible to predict the requested view before the user actually requests it. In the present invention, the view(s) that the user is likely to next request are preloaded while the user is reading the displayed view.
[0049] Thus, in one embodiment of the present invention, the view or views (i.e., anticipated view(s)) that are likely to be next requested by the user are “preloaded” (e.g., in the background) to the extent permitted by the time the user spends reading or studying the display view. When the user does request that a different view be displayed (i.e., the user requests a “requested view”), the requested view can be very quickly displayed on the monitor if it has already been preloaded into memory. Thus, if the requested view is one of the anticipated views, the database system, is able to quickly respond to the user's request for the requested view.
[0050] As shown in FIG. 3, while the user is reading or studying the display view 101A, view 201A is identified as an anticipated view (signified by the arrow from view 101A to view 201A). View 201A is likely to be requested by the user because it is the first view of the “next” search document (as defined by the ordering characteristic) following search document 100A. And while the display view 101A is being viewed by the user, the database system will preload view 201A from the database into memory, before it is actually requested by the user. After view 201A is preloaded into memory, the input device is checked to see if the user has requested that another view be displayed. If the user has requested that a requested view be displayed, the database system checks to see if the requested view has been loaded into memory (e.g., as the preloaded anticipated view). If the requested view is view 201A, it will have been loaded into memory as the anticipated view, so view 201A is retrieved from memory and displayed on the monitor. Since loading the requested view from memory is much faster than loading the requested view from the database, the time required to respond to the user's request for the requested view is shortened dramatically. If the requested view is not in memory, however, it must be retrieved from the database.
[0051] Instead of loading the entire anticipated view before checking the input device, in other embodiments of the present invention the input device is monitored during the time the anticipated view is being preloaded into the database. If the user requests a requested view, the preloading of the anticipated view stops and the user's request is serviced. This ensures that the system is very responsive to the user's input. Such an embodiment can be implemented by checking the input device each time a segment (i.e., a portion) of the anticipated view is preloaded. If the computer retrieving information from the database is running a multitasking and/or multithreading operating system, such an embodiment can alternatively be carried out using the various techniques appropriate for such an operating system.
[0052] FIG. 4(a) shows a situation where view 10A (shaded) is the display view, and the retrieval system has identified four views 102A, 501A, 201A, and 401A as anticipated views. View 102A is likely to be requested by the user when the displayed view is view 101A because it is the next view in the document that the user is currently viewing. View 501A is a candidate for the requested view because it is the first view from a document (500A) that relates to the search document (100A) that the user is currently viewing. View 401A is also an anticipated view because the user might wish to view the document that represents the opposite extreme of the ordering characteristic (e.g., the oldest document). And as described above, view 201A is also likely to be requested by the user.
[0053] In the embodiment of FIG. 4(a), the retrieval system will attempt to load as many of these anticipated views as possible while the user is studying the display view 101A. If enough time passes before the user requests a requested view, the retrieval system may preload all four of the anticipated views, thereby enhancing the likelihood that the next requested view will be in memory.
[0054] Once the user issues a request for a requested view, the requested view is loaded from memory (or from the database, if necessary) and displayed on the monitor. The process of determining and preloading anticipated views then starts over. For example, if the requested view is view 201A, the display view will then become view 201A (shaded) as shown in FIG. 4(b). The anticipated views would also change, and might be identified as indicated by the arrows.
[0055] FIG. 5(a) shows another representation of four search documents showing term views 111, 112, 211, 212, 213, 214, 311A, 312A, and 411. In FIG. 5(a), a term view is a view that has at least one search term from the query. And as can be seen from document 100A in FIG. 5(a), the boundaries of these term views may or may not correspond to the boundaries of views 101A, 102A, 103A, and 104A. Term views may also be anticipated views because the user might request as a requested view the next view having one or more of the terms in the query. Some systems provide a command for this purpose (e.g., in Westlaw, the command is “t”).
[0056] FIG. 5(b) shows the representation of the four search documents showing other term views 171, 271, 272, 371, and 471. These term views are made up of a small number of words surrounding each occurrence of a search term in the search documents. Since the number of words surrounding the search terms is small, more than one set of words can fit on the screen at a given time. Thus, the term view in this embodiment includes information from different parts of the document. The “KWIC” display format in the LEXIS/NEXIS system operates similarly.
[0057] FIG. 6 shows another representation of the four search documents showing subdocument views 121, 122, 131, 141, 221, 231, 232, 233, 321, 331, 421, 431, and 441. The subdocuments are shown in FIG. 6 as 120, 130, 140, 220, 230, 240, 320A, 330A, 420, 430, and 440. A subdocument is any logically separable or identifiable portion of a document. For example, if a document is a judicial opinion, there might be subdocuments for the title and citation for the case, for each of the headnotes, for the opinion itself, and for any dissenting opinions. A subdocument view is a view within a subdocument.
[0058] Subdocument views may be anticipated views because the user is often particularly interested in a particular portion of the search documents. If the search documents consist of a series of judicial opinions, for example, a user may only wish to view, for each of the search documents, the subdocument for the majority opinion (and not the headnotes, dissenting opinions, etc.). Thus, it may be appropriate for the anticipated views to be drawn primarily from a particular type of subdocument.
[0059] In other situations, however, the user may only wish to see the first subdocument view for each subdocument. It would be appropriate in these situations for the anticipated views to be primarily the first views from the various subdocuments within each document.
[0060] The retrieval system of the present invention identifies anticipated documents by focussing on the current display view. The current display view gives clues as to which view might be requested by the user because the display view identifies the user's progress in browsing the search documents. In other words, the current display view identifies which search document in the sequence of search documents is currently being viewed. This information is useful because the search document immediately following and preceding the current search document (as defined by the ordering characteristic) is often the search document next requested by the user.
[0061] The view displayed just prior to the displayed view might also be a consideration in determining the anticipated views if it tends to show a pattern that can identify the user's next requested view. For example, referring to FIG. 6, if the user requests view 131 of search document 100A, and then requests view 231 of search document 200A, the retrieval system can consider these two consecutive display views and determine that an appropriate anticipated view is view 331 of search document 300A. View 331 is the first view of subdocument 330A, which could be the same type as subdocuments 130 and 230, the two subdocuments previously viewed by the user. Since the goal is to accurately predict the next view, considering the views that the user requested in the past may be helpful if it tends to identify the views that the user will request in the future.
[0062] In general, any appropriate adaptive prediction scheme can be used that uses the user's history of requested views (and display views) to accurately determine which views are likely to be next requested by the user. It might be appropriate in some cases to consider many display views in determining appropriate anticipated views. Longer histories may tend to identify patterns that would not show up if only a small number of recent display views are considered.
[0063] Tendencies can even be monitored over more than one research session in situations where a particular user or group of users tend to request views in a particular pattern each time research is done. In addition, the user could be prompted to indicate the type of research being undertaken, which may give clues as to what type of anticipated views are appropriate for efficient operation. Finally, the particular databases used or type of research being done can be monitored by the database system and advantageously taken into account in determining anticipated views.
[0064] In the preferred embodiments of the present invention, the anticipated views are drawn from both related documents and search documents. A fundamental distinction between related documents and search documents is that related documents are statically-related to the search documents, whereas search documents are dynamically-related to one another. This difference is significant because unlike statically-related documents, no predefined link needs to be set up for search documents. A statically-related document is always associated with a particular document, regardless of the query (the related document is therefore statically-related). The search documents, on the other hand, are related to each other by the query. Since the query changes with each search, the search documents are considered dynamically-related to one another.
[0065] Some of the recent CD-ROM products have implemented features such as hyperlinked text, and timeline-linked text (clicking on a timeline item will take the user to a relevant article). See The Top 100 CD-ROMs, PC Magazine, Sep. 14, 1994, p. 115. Links of this nature are static because they always apply and do not depend on any particular query run by the user.
[0066] The search documents are ordered by an ordering characteristic as described previously. Thus, when a “next document” is requested, it is assumed that the search document requested by a “next document” command is the search document that is “next” according to the ordering characteristic. If the search documents are ordered by publication date, for example, the “next document” will be interpreted as a request for the search document with the next oldest publication date.
[0067] In one embodiment of the present invention, it is possible to make a number of different ordering characteristics available for use by the user in browsing the search documents. For example, FIG. 7 shows seven documents labeled “a” through “g” ordered according to four different ordering characteristics. When the display view is in document “a,” the “next document”command can be a request for four different documents (i.e., “b,” “e,” “f,” or “c”), depending on the particular ordering characteristic used. More than one ordering characteristic must therefore be considered when determining anticipated views if the user is capable of moving to a “next document” in the context of more than one ordering characteristic. This feature can be enabled by an input device command that allows the user to select the desired ordering characteristic.
[0068] The present invention is applicable to single-user, multiple-user, and many-user databases, but the present invention is most effective when used in connection with single-user databases. The efficient operation of the invention depends on being able to retrieve data from the database very frequently, perhaps continually. The present invention is quite effective with single-user databases such as those on CD-ROM or other mass storage devices (this might also include a hard drive implementation). In a single-user database, no other demands are being made on the database by the other users, so the database is often idle.
[0069] But since a many-user or multiple-user database must be shared among more than one user, such a database will often be receiving simultaneous and continual requests for data. Databases in such a system are rarely idle, so there is little time to preload anticipated views into memory. In such a situation, the present invention will not be as effective in improving the response time to users' requests for requested views. But in many-user or multiple-user database systems where the database is not as busy, the present invention can be effective in reducing response times to users' requests for information.
[0070] FIG. 8 is a flow chart of the operation of the database system in one embodiment of the present invention. A system in one embodiment of the present invention begins by executing a query to identify the search documents. This step is carried out by search logic 51. The remaining steps shown in FIG. 8 (described below) are carried out by retrieval logic 52. Both the search logic 51 and the retrieval logic 52 are often software, but need not be. As one skilled in the art will recognize, in a software implementation the search logic 51 and the retrieval logic 52 may or may not be integral or intertwined parts of the same computer program.
[0071] As dictated by the retrieval logic 52, the database system then loads into memory a view from one of the search documents. See FIG. 8. This first display view is then displayed on the monitor. Normally the user will take a few moments to read or study the display view. During this time, one or more anticipated views are identified. The anticipated views are views that the user is likely to request be displayed on the monitor after the display view.
[0072] The database system then begins to preload these anticipated views into memory from the database, while also continually monitoring the input device to determine if the user has issued a request to display a different view (i.e., a “requested view”) on the monitor. Anticipated views are loaded into memory until the user requests a requested view.
[0073] When the user does makes such a request, the database system then determines whether the requested view is in memory. The requested view may be in memory because it could have been preloaded into memory as an anticipated view. If the requested view is in memory, the requested view becomes the new display view, and it is displayed on the monitor. But if the requested view is not in memory, the requested view must first be loaded from the database before it can be displayed on the monitor as the display view.
[0074] The anticipated views are a function of the display view because the views that the user is likely to request depend to some degree on the view the user is currently reading. In other words, those views that are anticipated views when view 101A is the display view are not likely to be the same as the anticipated views when view 202A is the display view. Therefore, as shown in FIG. 8, the anticipated views are determined each time the display view changes.
[0075] When the display view is changed, the anticipated views for the prior display view can remain in memory so that they are available if they are ever requested by the user. But if memory is limited, the anticipated views for the prior display view can be deleted from memory, preferably in an efficient matter (erg., anticipated views common to both the new display view and the prior display view are not deleted from memory). It is best to delete those views that are not likely to be requested by the user. It may also be appropriate to consider whether a view is likely to become an anticipated view in the future.
[0076] FIG. 9 shows a flow chart representing another embodiment of the present invention where anticipated views from prior display views are deleted if memory is full. The views deleted are those that are not anticipated views for the new display view. This will presumably make room for new anticipated views to be preloaded into memory (if not all of the anticipated views are already in memory).
[0077] The number of anticipated views for a given display view does not have to be a predetermined or constant number, but rather can vary depending on memory available. Typically, the number of anticipated views for a display view is a trade-off between the amount of memory available and the desired speed of retrieval. In instances where memory is plentiful, where the number of search documents is few, and/or where the search documents are small, it may be possible for all of the search documents to be completely loaded into memory. In such a situation, the number of anticipated views for a given display view could be as high as the total number of views in the search documents. At the other end of the spectrum, there might be only one or two anticipated views for each display view if memory is limited.
[0078] Embodiments of the present invention can vary as to how anticipated views are preloaded into memory. In the embodiments of FIGS. 8 and 9, one anticipated view at a time is preloaded into memory, and the retrieval system does not begin preloading a second anticipated view into memory until the prior anticipated view is completely preloaded into memory. In other embodiments, anticipated views are simultaneously preloaded.
[0079] Simultaneous preloading of multiple anticipated views can be done in a number of ways. In a multitasking operating system, for example, an appropriate time-slicing procedure can be used to preload the anticipated views so that they are preloaded simultaneously. In another embodiment, one segment from each anticipated view is preloaded in turn, and the cycle is repeated until all the anticipated views are fully preloaded into memory (or until the user's request for a requested view interrupts the preloading process). A segment is any portion of an anticipated view, such as one or two lines or even a single byte of the anticipated view.
[0080] FIG. 10 shows a simple implementation of the simultaneous preload concept, where the database system preloads a segment of a first anticipated view into memory, and then preloads a segment of a second anticipated view into memory. These steps continue until either the user requests a requested view, or both anticipated views are fully preloaded into memory. When the user requests a requested view, the database system checks to see if that requested view is in memory. If the requested view is only partially preloaded into memory, that portion in memory can be written to the monitor and the remaining portion loaded from the database. The response time in this situation will still be better than if the entire requested view has to be loaded from the database.
[0081] In another embodiment of the invention, the use of profile information is employed to assist in the selection of views or documents to preload, as illustrated in FIGS. 11-12, 13a-13e, and 14-16. For example, FIG. 11 is a diagram of the relationships between six objects or documents 301-306. The six documents are linked to each other in the manner shown and hereinafter described. Document 301 contains three links (310, 312, and 314); one to each of the documents 302, 303, and 304. Document 302 contains two links, one link 316 to document 305, and another link 318 to document 306. Document 305 contains a link 320 back to document 302, and document 306 contains a link 322 to document 304. Each of these documents is stored on a server within a network, and may incorporate or have embedded within it objects stored on other servers. The documents 301-306 may be stored on the same server, or may be stored on various computers distributed throughout the network.
[0082] FIG. 12 shows a representation of a video display screen 404 for a computer such as that of FIG. 1. The area 404 represents the area on a screen within which images, text, video, and other types of data or multimedia objects can be displayed and manipulated. On the display 404 shown in FIG. 12, a number of icons or objects 402 are arranged, along with another type of object, window 406. The window 406 is a representation of a document retrieval, browsing, and/or viewing program that is used to view information either stored locally on the computer or retrieved over a network. The window 406 has a title area 408 that displays the title of the document being displayed. The title area 408 could also display the location or address of the document being displayed, or also the universal resource locator of the document being displayed. Alternatively, an additional area within the window could be used for displaying the universal resource locator. The contents of the document are shown in displayed within the window 406 in FIG. 12, but it should be understood that the contents could be displayed in other ways. For example, the contents could be displayed on the entire desktop, or a portion of the desktop. In another embodiment, the contents might be scrolled on the screen, perhaps under other windows. In addition, it should be understood that where a document has only a single view, or is treated as having only a single view, the “document” essentially becomes the same as the “view.” In such a situation, a scroll bar (not shown) may be used to allow a user to effectively expand the size of the display, thereby allowing the user to see the entire document/view.
[0083] Shown within the document viewing area of the window 406 in FIG. 12 is the contents of the document 301 from FIG. 11. The document 301 has been displayed in the window 406 in response to a user query, which might involve a key word search or might involve the user specifying the identity, address, or resource locator of document 301. The document 301 could be also be displayed within the window 406 in response to the selection of a link in another document (not shown) that points to the document 301.
[0084] FIG. 13ais flow chart representing the operation of one embodiment of the present invention in which profile information is used to assist in the selection of documents to preload. In FIG. 13a, the documents 302 and 303 are assumed to be stored on the network on a (preferably) remote database server. At 501 in FIG. 13a, document 301 is retrieved from the server by a document retrieval program that executes on a client computer, such as, for example, the computer 257 in FIG. 1b. The document 301 may be stored on any of the other computers shown in FIG. 1b, including computer 257. Along with the document 301, the document retrieval program retrieves profile information that is preferably (but not necessarily) embedded within or is stored with document 301. The profile information can be used to provide information about document 301, including information about documents that are related to document 301, as described below.
[0085] At 502, the document viewing program renders document 301 in the window 406, as shown in FIG. 12a. Once document 301 is retrieved, the viewing program begins at 504 retrieving from the network the document 302. During this time, document 301 continues to be displayed in window 406, and the user is free to read, scroll through, or otherwise interact with the document 301 shown in the window 406 in FIG. 12a. Thus, document 302 is retrieved over the network (504) and stored into the memory or local storage (505) while the user is viewing document 301.
[0086] After document 302 has been retrieved, if the user has not requested (e.g., through the input device) at 506 that another document be displayed, the document viewing program at 508 retrieves document 303 over the network, and this document is then stored in memory or local storage. The document 301 is still displayed in the window 406 at this point. If the user still has not requested that another document be displayed at 510, the document 304 is retrieved from the network and stored in memory or local storage by the document viewing program in 512.
[0087] At 514, the document viewing program in the embodiment of FIG. 13astops preloading documents, and waits until the user requests that a new document be displayed. When the user does request that a new document be displayed in the viewing program at 514, the viewing program determines at 516 whether the requested document is one of the documents that has already been retrieved and stored in local storage. If so, then the locally-stored version of the requested document is retrieved from memory or local storage at 518. The locally-stored version of the requested document is then checked at 519 to see if it is out of date. If the requested document has content that may change often, it may be that the version of the requested document that is stored in local storage is not sufficiently new and is out of date or “stale.” This condition can be determined by monitoring the amount of time since the document was originally preloaded, or by inspecting the time stamp on the requested document stored on the network and comparing it to the time stamp for the locally-stored version to determine whether the locally-stored version has changed.
[0088] If the locally stored version of the requested document at 519 is not out of date, then it is displayed at 524. If the preloaded version at 519 is out of date, or if the requested document has not been preloaded at all (516), then the requested document is retrieved over the network and is displayed at 524.
[0089] In another embodiment, the document viewing program may continue preloading additional documents at 512 in FIG. 13a. For example, the document viewing program could begin to preload the documents that are linked to by the documents that are already preloaded (i.e., documents 302, 303, and 304). In the set of documents shown in FIG. 11, this would mean that the document viewing program would download over the network additional documents 305 and 306. Thus, the present invention need not be limited to the preloading of only a single level of linked documents, but rather, could extend to the preloading of two or more levels.
[0090] As described in connection with FIG. 13a, the document viewing program retrieves over the network documents 302, 303, and 304 while the user is viewing document 301. And as shown in FIG. 13a, document 302 is preloaded first, followed by document 303, and then by document 304. In some embodiments, the document viewing program executing on the client computer in FIG. 13auses the profile information to determine the order in which the documents 302, 303, and 304 are to be retrieved. In other words, in some embodiments, the database server determines the order in which the document viewing program executing on the client preloads the links within document 301. This procedure can be quite effective because the database server may have useful information that can help to predict the documents that the user will request be displayed at the client computer. For example, a server that keeps track of the frequency that users select the links within document 301 may find that one or two links are selected very often, whereas other links are selected rarely. The server can use this information to instruct the client as to the most efficient order in which to preload documents.
[0091] FIG. 14 is a chart illustrating one example of the type of profile information that could be provided with document 301 at 501 of FIG. 13a. As shown in FIG. 14, for each of the documents identified in the profile information, the historical percentage of users that have selected the document are identified. The first three documents (302, 303, and 304) are documents that are linked to by the document 301 as shown in FIGS. 3 and 4. The fourth document (document 319) is not linked to or otherwise related to document 301, but the profile information nevertheless tells us that 2% of the people request document 319 when document 301 is displayed. Thus, the profile information tells us that document 302 is, historically, the most likely document to be selected. The document viewing program can use this information to ensure that document 302 is preloaded when document 301 has been rendered in the window 406 because at least according to this statistical information, document 302 is likely to be requested by the user who is viewing (or who has at least retrieved) document 301.
[0092] Other data that might be included in the document profile might be the server or database in which each document is stored. This information is shown in FIG. 14, and identifies the document 302 as being from the server “gaylords.com,” and document 303 as being from the “same” database server, which means the database server from which document 301 has been retrieved. Normally, the profile information of FIG. 14 would be stored in a particular format or data structure, or even as source code, and either embedded within the document 301, or downloaded by the document viewing program along with the document 301.
[0093] In operation, the server sends to the document viewing program the information of FIG. 14, and the document viewing program can choose to ignore it, or could choose to act upon it in some way. Thus, the document viewing program in one embodiment engages in some form of interpretation of the profile information and it exercises some control over how the information is used. In another embodiment, however, the profile information could simply consist of a list of documents that the document viewing program uses to select what documents to preload. The list of documents might be ordered so the document viewing program could determine relative priorities among the documents, but the document viewing program may not engage in interpretation of any statistical data or other data sent from the server. Such an embodiment may be implemented by actually programming a program embedded within a document to retrieve certain documents, thus effectively hard-coding the documents that are to be preloaded. Another embodiment may use a program embedded within an object or a document that reads a parameter list and uses the parameter list to select the documents to be preloaded. Where the profile information is not used, some type of predefined procedure could be followed for selecting documents to preload, and this procedure may involve preloading the documents that are linked to by the document 301 (the displayed document).
[0094] FIG. 15 is a flow chart which illustrates how the profile information might be used in an embodiment of the present invention. At 594, the document 301 is retrieved over the network, and at 595, the profile information for document 301 is retrieved over the network. The profile information is then analyzed at 596 to determine which documents to preload when document 301 is being displayed. At 597, the profile information is further analyzed to determine the order in which the documents identified at 596 should be preloaded. Thus, in this embodiment, the profile information not only identifies the order in which to preload documents, but also identifies at 596 the documents that are to be preloaded.
[0095] FIG. 13bis a continuation flow chart of FIG. 13a, where the user has requested that document 302 be displayed. In other words, the requested document at 516 of FIG. 12ais document 302. Thus, initially in FIG. 13bthe document 302 and associated profile information associated with document 302 is retrieved at 529 and then displayed at 530 within window 406. At 532, the viewing program checks to see if the user has requested that another document be displayed. If not, document 305, which is linked to by document 302 (see FIGS. 3 and 4b), is retrieved from the network and stored in local storage. At 536, the viewing program checks again to determine whether the user has requested that another document be displayed, and then proceeds to preload document 306, which is the other document linked to by document 302. In this particular embodiment, the order in which documents 305 and 306 are preloaded is dictated by the profile information.
[0096] When the user does request that a different document be displayed in FIG. 13b, the viewing program determines at 542 whether the requested document has been already loaded into local storage. If it has been loaded into local storage, the requested document is retrieved from the higher-speed local storage (544) and the contents of the requested document are analyzed to determine if the information in the preloaded version is out of date (545). If not, the preloaded version of the document is rendered in the window 406 (546). Otherwise, the document is retrieved over the network (548), and then rendered in the window 406 (546).
[0097] FIG. 13cis a continuation of the flow chart of FIG. 13b, where the user has requested in FIG. 13bthat document 306 be displayed, and at 579 the document 306 and its profile information is retrieved, and then at 580 of FIG. 13c, document 306 is displayed. At 582, the viewing program checks to see if the user has requested that another document be displayed. If not, another document is preloaded into the memory unit or into local storage at 584. As can be seen in FIG. 11, document 306 contains only link 322, which is a link back to document 304. Thus, at 584, the document 306 may be preloaded into memory or local storage if it is still in memory from a preloading operation at 538 in FIG. 13b. If it is in memory, it is not necessary to preload it, so the document viewing program can preload from the network some other document that the user may be likely to request. Such a document could be identified in the profile information for document 306 (as described above), or such a document could be a document that was linked to a previously-viewed document, but wasn't fully preloaded into local memory. For example, if in FIG. 13adocument 303 was not preloaded, this document could be preloaded at 584 because it may, at some point, be requested by the user. Alternatively, the document preloaded at 584 may be one of the bookmarked documents maintained by the document viewing program (e.g., at the client), or a document from some other popular site.
[0098] When the user requests a new document, the document viewing program checks at 586 to determine whether the requested document has been preloaded (586). If it has, the preloaded version is retrieved at 588 and analyzed to determine whether it is out of date at 589. If the preloaded document is not out of date, it is displayed at 590. Otherwise, the document is retrieved over the network at 592, and displayed at 590.
[0099] FIG. 13dis a partial flow chart in an alternate embodiment of the present invention that can be used to replace 504 in FIG. 13a. FIG. 13dillustrates that each document normally contains a number of objects, and in order to retrieve from the network the entire document, each of these embedded objects must be also be retrieved. In the embodiment of FIG. 13d, document 302 comprises a base document which is retrieved over the network at 550. The base document 302 contains references to the embedded objects within document 302. When the base document is retrieved from the network, it is analyzed at 552 to determine the additional embedded objects (if any) that must be retrieved to complete the document. If document 302 has three embedded objects, each is retrieved from the network as shown in FIG. 13bin succession (steps 554, 556, 558).
[0100] In an alternate embodiment, shown in FIG. 13e, a separate thread of execution is started for retrieving each of the embedded objects. This embodiment recognizes that it may be more efficient to download the embedded objects simultaneously, rather than one at a time as shown in FIG. 13d. The embodiment of FIG. 13d, however, has the advantage that it may be able to completely download at least one of the embedded objects before it is interrupted by a request to display another document. Depending on the implementation of the viewing program, a fully preloaded object may be more useful than a partially-preloaded object. Preloading documents simultaneously may increase the chance of having a large number of partially-preloaded objects, and fewer fully-preloaded objects. Thus, where partially-preloaded objects are less useful than fully-preloaded objects, the embodiment of FIG. 13dmay be more efficient than FIG. 13e.
[0101] FIG. 16 is flow chart of the operation of a system in which document 301 and its associated profile information is retrieved at 601, and the document 301 is displayed at 602. The documents 302 and 303 are then preloaded in two separate threads of execution (steps 604 and 606) so that they are retrieved from the network substantially simultaneously. Unlike FIG. 15, in the embodiment of FIG. 16 the document viewing program does not preload document 304 while document 301 is displayed. The decision not to preload document 304 may be based on the profile information for document 301 retrieved over the network at 601 in FIG. 16. For example, the profile information could instruct the document retrieval program to not preload document 304, or the profile information could indicate that the document 304 has been (historically) so rarely selected by other users that the document retrieval program decides not to retrieve document 304.
[0102] A third thread of execution in FIG. 16 (610) monitors the user's actions (e.g., manipulation of the input device) to determine if the user has requested that a different document be displayed. When the user does request a document at 610, the system (e.g., the document viewing program) determines (612) whether the requested document has been at least partially preloaded. Where it has not, the requested document is retrieved over the network at 618 and displayed at 616.
[0103] However, if the requested document has been at least partially preloaded, the preloaded version is checked for staleness at 617. At 613 the document viewing program determines whether the requested document has been partially or fully preloaded. If the requested document has been fully preloaded, it is retrieved from local storage (614) and rendered on the display (616). If it has been only partially preloaded, the partially preloaded version is retrieved from local storage (620), and any portion not in local storage is retrieved from the network (622), and then rendered on the display (616).
[0104] In some situations, it may be useful to have the user exercise some direct control over the preloading process. For example, FIG. 17ashows a screen 704 having a window 706, which includes a title bar 714 and an area 717 in which to visually render the contents of a document. A cursor 724 corresponding to a pointing-type input device is also shown in the embodiment of FIG. 17a. The document shown in the window 706 includes hypertext links 718, 720, and 722, and the document also comprises graphical object 707, which includes area 709. The graphical object 707 also acts as a link to another document. Also shown in the window 706 are buttons 708, 710, and 712, which each correspond to one of the hypertext links. Button 708 corresponds to link 718, button 710 corresponds to link 720, and button 712 corresponds to link 722.
[0105] In FIG. 17b, the cursor 724 has been moved to the button 712 so that the button 712 is selected. Upon selection, the document viewing program begins preloading the document linked by the “forecast” hyperlink 722, which corresponds to the button 712. The “forecast” document is not yet displayed within the window 706, however, and the “News Items” document shown in FIGS. 17aand 17bcontinues to be displayed. While the document corresponding to link 722 is retrieved over the network, the progress of the preloading operation is displayed on the button 712. At the point shown in FIG. 17b, the document corresponding to the “forecast” link is 7% retrieved.
[0106] FIG. 18ais a flow chart illustrating the operation of an embodiment of the present invention that is similar to that described in connection with FIGS. 17aand 17b. Initially at 802, a document is displayed by the document viewing program. The document viewing program then alternatively monitors the user's input to determine whether the user has selected a document to preload (804) or a document to be displayed (808). A document is selected to be preloaded by the user when one of the buttons 708, 710, or 712 is selected, or when area 709 within the graphical object 707 is selected. Upon such a selection, the document corresponding to the selected button or to the selected graphical object is retrieved over the network and stored in local storage (806).
[0107] In the embodiment of FIG. 17a, the user requests a document to be displayed by selecting a hypertext link or by selecting the graphical object 707. When the user has requested a document to be displayed, the viewing program determines at 810 whether the requested document has already been retrieved into local memory or storage. If it has been preloaded, it is retrieved from local storage (816), and displayed in the window 706 (814).
[0108] In some embodiments, the document may also be checked at 818 to determine whether it is sufficiently new or current. If its download date, modification date, or other information indicates that the contents of the document are not sufficiently new, or are out of date, the requested document is again retrieved over the network at 812.
[0109] FIG. 18billustrates an embodiment of the present invention in which a document is displayed at 830 by the viewing program, and then one or more threads of execution begin preloading the documents that are linked to by the displayed document (832). Another thread of execution monitors the user's input to determine whether the user has selected a link to preload (834) or whether the user has selected a link to display (836).
[0110] When the user selects a link to preload at 834, such as by selecting one or more of the buttons 708, 710, or 712 in FIG. 17a, the viewing program begins preloading the selected link, and does so at a higher priority at 840 than any of the other links that are being preloaded at 832. In other words, when the user selects a link to be preloaded, the viewing program allocates more resources to preloading the selected document at 840 than to any other preloading operations it is carrying out on any other documents at 832.
[0111] Where more than one link has been selected by the user, each could be preloaded at a priority higher than that of the documents being preloaded at 832. In another embodiment, the document most recently selected for preloading could be given a priority higher than any other, so that the resources of the document viewing program are being applied to the preloading of the most recently selected-document.
[0112] Once the user'selects a document to be displayed, the viewing program determines at 842 whether the document has been preloaded into local storage. If so, the preloaded version is retrieved from local storage (848), and displayed (846). Otherwise, the requested document is retrieved over the network (844) and displayed (846).
[0113] In the embodiments described in FIGS. 18aand 18b, the user selects the document that he or she wishes to preload, and in the embodiments of FIGS. 17aand 17b, this is done by selecting button that corresponds to the desired link. In other embodiments, selecting the link that the user wishes to preload can be done in a number of other ways. For example, selection of a link to preload could be carried out by simply passing the mouse or pointing device cursor over the desired link or over an object that corresponds to the link. Such an action could communicate to the document viewing program the link that the user wishes to preload. In another embodiment, the user could select the desired link with a right mouse click (or some other keyboard or pointing device action), or by directing the document viewing program to preload a given link by selecting an appropriate option from a menu that is displayed when the link is selected with the pointing device.
[0114] In FIG. 17a, selection of the document linked to by the graphical object 707 is carried out by the selection of the space 709 within the object 707, or by passing the cursor over the area 709 in FIG. 17a. Selection of any other portion of the object 707 constitutes a request that the document corresponding to the document to the object 707 be displayed, rather than preloaded. FIG. 17bshows one way in which the progress of the preloading can be communicated to the user. FIGS. 17c, 17d, 17e, and 17fshow other embodiments in which the progress being made in the preloading operation is communicated to the user. In FIG. 17c, the graphical object 707 from FIGS. 17aand 17bhas been selected for preloading, and a progress gauge 717 has a shaded area 719 which is used to show what portion of the document has been preloaded. When the shaded area 719 fills the gauge 717 entirely, the document linked to by the graphical object 707 has been preloaded.
[0115] The button 710 in FIG. 17doperates in a manner similar to the button 712 of FIG. 17b, but it changes colors to indicate the progress of the preloading operation. For example, the button 710 could get progressively darker (or lighter) while the linked document is being preloaded. FIG. 17eshows a text button 760 that is used as a hyperlink. Selection of the button for preloading (e.g., by passing the cursor over the button) causes the button to change color or shade (see FIG. 17f) as the preloading proceeds. Any type of visual or audio progress indicator could be used to indicate progress of the preloading, and is useful to the user because he or she will know when a desired document has been preloaded. The user can continue to read or interact with the currently displayed document until the visual or audio indicator signifies that the document has been preloaded. Thus, the user can be assured that when the preloaded document is selected for display, it will be quickly displayed.
[0116] In some document retrieval systems, the user may incur a cost for each document or set of information that he or she retrieves from a database or over a network. In such a system, preloading documents before they are requested by the user could incur fees for documents that the user has never intended to see, use, or retrieve from the network. In other words, some documents may be retrieved in such a system simply because they are linked or otherwise related to one of the documents that the user did retrieve. This can undesirably increase costs for the user.
[0117] FIG. 19 is a flow chart illustrating how an embodiment of the present invention can effectively operate in an environment where the user incurs fees for each document or set of documents retrieved over the network. In this example, when a document is displayed at 902, the document viewing program proceeds to preload one or more documents that are linked to the document that the user is viewing. However, the viewing program does not preload the version of the linked documents that incur a fee. Instead, the viewing program preloads a free (or reduced cost) encrypted version of the linked document(s). This encrypted version is distributed free or at a lower charge because it is unreadable (or at least difficult to read) to anyone that attempts to view the encrypted version. However, the encrypted version can be easily converted into the normal, readable version of the content or the document by processing the encrypted version of the document with a password or a key.
[0118] When the user selects a document to be displayed at 906, the viewing program determines at 908 whether an encrypted version of the requested document has been preloaded. If so, the viewing program retrieves the password or key required to decrypt the encrypted version of the document, and at that time, the cost of retrieving the document is incurred at 910. The encrypted version of the document stored locally is decrypted at 912 and then displayed at 914.
[0119] By retrieving only the password or key over the network and then.decrypting the locally-stored encrypted version of the requested document, the document will typically be displayed much more quickly than if the entire document would have to be retrieved from the network. Normally, the size of the key will be much smaller than the size of the document. Retrieving only the key, and processing the encrypted document at the client will therefore typically be much faster than retrieving the unencrypted version of the document over the network upon receiving a request for it.
[0120] The use of the procedures described herein may, in some environments, substantially increase the number of requests that are issued to network servers, and may also increase the amount of bandwidth required for a given network. This can be exacerbated where each document has embedded within it additional objects that must be separately requested from the server. Thus, it may be desirable to implement techniques to alleviate, eliminate, or avoid these effects. In one embodiment of the present invention, each time a request is issued to a network server, additional information is included within the request so that the database server (or any other network hardware or resources) is notified of the type of the request. This will allow requests to be prioritized so that server and/or other network resources are not allocated to tasks that may have less priority (e.g., a request to preload a document) than other tasks (e.g., a normal document request).
[0121] FIG. 20ais a flow chart of a system in which the document viewing program communicates to the database server (or to the network itself) a priority for each request. At 1102, the document viewing program issues a normal priority request to the database server for document A. The database server responds to this request, and at 1104, document A is retrieved over the network by the document viewing program. When it is received, it is displayed by the document viewing program at 1106.
[0122] The document viewing program then starts a thread that monitors the user input at 1108 to determine whether the user has requested a document for display. Another thread is also started, and this thread at 1120 issues a low priority request to the server for document B (one of the documents it seeks to preload). The user at this point has not requested that document B be displayed, so the retrieval of document B is done based on the expectation that the user may wish to view document B at some point. For this reason, the request for document B is issued on a low-priority basis. (Document B may be a document that is linked to document A, that is identified in profile information, or that is otherwise related to document A.) When the server responds to the request, document B is downloaded over the network at 1122, and stored locally at 1124.
[0123] The low-priority request allows the network server to respond to other normal or high priority requests in advance of responding to the low-priority request for document B. This can be used to ensure that when the user actually requests a document from the server, the server will service that request before other low-priority requests by either that user or by other users. This information can also be used by the network hardware (e.g., network routers) itself to prioritize the routing of the requests or the routing of packets of data.
[0124] When a request that a document be displayed is made by the user at 1108, the document viewing program determines whether the requested document is in local storage at 1110. If it is, it is retrieved from local storage at 1116, and displayed at 1118. However, if the requested document is not stored in local storage, a normal-priority request is issued to the server at 1112. The request is a “normal” priority request because the user has actually requested a document, in contrast to the request made at 1120 of FIG. 20a. The document is then retrieved over the network at 1114, and then displayed at 1118.
[0125] FIG. 20bis another embodiment of the present invention that deals generally with the types of problems addressed in FIG. 20a. After document A is displayed at 1130, a thread that monitors whether the user has requested a document for display is started at 1132. Another thread is started at 1140 to determine whether the server on which document B is stored is busy. If it is, a wait state is entered at 1141 so that requests are not issued to the server over the network. This procedure thus preserves network and/or server resources. After a period of time, the server is then checked again. When the server is not busy, document B is retrieved over the network at 1142, and stored on the client computer at 1144.
[0126] When the user requests a document for display, the document viewing program determines whether the requested document has already been preloaded. If necessary, the requested document is retrieved over the network at 1136; otherwise, it is retrieved from local storage at 1140. After it is retrieved, it is displayed at 1138.
[0127] FIG. 20cis a flow chart of an embodiment of the present invention in which an anticipated document, document B, is stored in a file along with the objects that are embedded within the document B, are referenced by the document B, or are linked to by document B. By downloading such a file, the number of requests that must be issued to the server can be reduced. And if data compression is used to reduce the size of the file at the server and decompress the file at the client, the number of bits that must be downloaded to the client computer can be reduced.
[0128] Once document A is displayed at 1148 in FIG. 20c, the document viewing program monitors the user at 1150 for a request to display a new document. At the same time (i.e., in another thread of execution), an object that contains document B and the objects embedded within it is retrieved over the network at 1160. This object may also include one or more documents that are linked to by document B. When the object is downloaded, it is parsed at the client computer at 1162 so as to extract document B and the embedded objects, which are then stored at 1164 on the client computer. When the user requests a document for display, the document viewing program determines at 1152 whether the requested document has already been preloaded. If necessary, requested document is retrieved over the network (1154), but if possible, it is retrieved from local storage (1156). After it is retrieved, it is displayed at 1158.
[0129] The present invention is suitable for implementation as an ActiveX or Java control, which could be downloaded as part of a web page into a browser or an operating system for execution on a client computer. In such an embodiment, there may be security restrictions placed on the downloaded control. Included in the original specification is an outline of a Java program or psuedocode for applet, written in Java that can be inserted into a web page, and appears on the web page as a button that it is associated with an HTML link. When the button is selected, the document corresponding to the associated link is preloaded onto the client, and the base HTML document and at least some of the embedded objects are stored on the client's local file storage system. The client's file system is typically much faster than the network.
[0130] In some Java environments, the client's local file system is not accessible because of security restrictions if the applet is downloaded from a remote host. These security restrictions can be avoided by using an insecure environment, or by using a code signing technique that allows the user to verify the author of the applet. Once the code is identified as being written by a trusted author, the security restrictions can be safely eased or eliminated.
[0131] In another embodiment, a secure means of accessing the client's file system can be used to securely and safely store data on the client's file system. In such a system, the applet may only be allowed to write files to certain directories. The applet may also be limited to reading only files that it had created. One such secure file system for Java has been referred to as “protected domains,” and can be useful in implementing some embodiments of the present invention.
[0132] Included in the original specification is another listing of Java code/psuedocode in an implementation of the computer program or applet that does not use the local file system for storing preloaded documents. Instead, the Java program included in the original specification stores preloaded documents in memory, and implements a web server on the client to serve the documents back to the document viewing program running on the client. Thus, when the user selects a link, the link is redirected to the server running on the client, and that local server responds with the preloaded document if it is available. The document viewing program would, in effect, be retrieving preloaded documents from local memory, thereby making access to preloaded documents quite fast. Such an implementation may also avoid the security restrictions placed on accesses to the local file system in some embodiments.
[0133] FIG. 21 is a flow chart that illustrates the high-level operation of the pseudocode included in the original specification. At 1202, a document is display, and a local document or object server is then set up at 1204. Two threads of execution are started, one to retrieve an anticipated document (document B) from the network and store it as a document capable of being served by the local server (steps 1220 and 1221), and another to monitor the user's actions to determine when the user has selected a document for display (1204).
[0134] When the user selects a document for display at 1206, the request is routed to the local server (1210) if the requested document had been stored locally. Otherwise, the a request for the document requested by the user is issued to the server (usually a remote server) on the network (1216). When the document is retrieved (or as it is retrieved), the document is displayed at 1214.
[0135] Because a web page control may have to be downloaded with each page, it may be desirable to implement techniques to speed the amount of time that a user has to wait for a document to be retrieved from the network. One such procedure is to embed a small applet into the web page that is downloaded by the user, where the small applet then retrieves a larger program that carries out the remaining steps. Such a procedure will allow the user to begin interacting with the web page after the small applet is downloaded, and will not require that the user wait for a larger program to be downloaded before interacting with the web page. Once the small applet is downloaded, the larger applet is downloaded in the background while the user is viewing or interacting with the web page.
[0136] FIG. 22 is a flow chart that illustrates the use of a small embedded program that retrieves a larger embedded program, and causes the latter to execute. At 1302, a document or object with an embedded initializing program stored within it is downloaded from the network. The document (or object) is displayed on the screen at 1304, and in a separate thread of execution, the initializing program is started at 1316. The initializing program retrieves supplemental program code over the network, and execution of this code is started at 1320. As indicated in FIG. 22, this new code retrieves anticipated documents over the network, also at 1320.
[0137] Because the initializing program is small, it takes relatively little time to download, and the document viewing program is able to promptly start the execution of the initializing program. This may allow the display of the document at 1304 to take place more quickly. The effect is a more responsive program that does not cause the user significant delay while an applet implementing the present invention is being downloaded.
[0138] Many embodiments of the present invention have been described as storing preloaded documents into local storage at the client computer. However, the present invention need not be limited to contexts in which information is stored at the client computer or in local storage at the client computer. The present invention is useful in any environment where it is possible to store preloaded information in an area where access to the preloaded information is faster than that of the original location for the information. For example, FIG. 23 shows a network where computer 1401 is preloading (1412) a document 1440 on server 1402 while viewing-another document on the network. In the embodiments described previously, the document 1440 is retrieved over the network and stored in local storage at the computer 1401. However, other embodiments of the present invention can be performed by storing the preloaded document elsewhere, but still in a location that can be accessed quickly.
[0139] An example is shown in FIG. 23 where the computer 1401 retrieves document 1440 from the server 1402 as part of a preloading procedure. At the direction (1412) of computer 1401, the preloaded document is retrieved (1410) and stored in the computer 1403, which is accessible by the computer 1401 over the LAN. Information on computer 1403 can be accessed by the computer 1401 quickly because these two computers are connected over a relatively fast (local) network. This is unlike the connection between the computers 1401 and 1402, which are connected over the lower-speed WAN.
[0140] When the preloaded document 1440 is stored on the computer 1403, it can be more quickly retrieved from computer 1403 than from computer 1410. Thus, significant enhancements to the responsiveness of the document viewing program can be made in the present invention, even if the preloaded documents or objects are not stored directly in local storage, but instead, are stored elsewhere where they can be retrieved quickly.
[0141] Some embodiments of the present invention have been described in the context of accessing the database and identifying search documents through a search term query. The present invention can be applicable in other research-related contexts where search documents are identified using another type of entry path. For example, a time-line can be used for locating information or documents that are associated with a given time or time-frame. Another information access method uses a topic tree that permits a user to choose from successively narrowing topics until the desired topic is located. It is possible for the present invention to be applicable even in other non-research contexts where similar preloading techniques may permit efficient navigation of information and/or short response times. The present invention can also be used in combination with caching systems where previously-displayed documents or views are stored for repeated use.
[0142] The present invention has been primarily described in the context of a general purpose computer implementation. As one skilled in the art will recognize, however, it is possible to construct a specialized machine that can carry out the present invention.
[0143] The additional references listed below are hereby fully incorporated by reference to the extent that they enable, provide support for, provide a background for, or teach methodology, techniques, and/or procedures employed herein.
[0144] Reference 1: Yellin, The Java Application Programming Interface: Volumes 1 & 2 (Addison Wesley 1996)
[0145] Reference 2: Campione, The Java Tutorial (Addison Wesley 1996)
[0146] Reference 3: Chappell, Understanding ActiveX and OLE (Microsoft Press 1996)
[0147] Reference 4: Denning, OLE Controls Inside Out (Microsoft 1995)
[0148] Reference 5: Brockschmidt, Inside OLE (2d ed. Microsoft 1995)
[0149] Reference 6: Graham, HTML Sourcebook (2d ed. John Wiley & Sons 1996)
[0150] Reference 7: Tanenbaum, Computer Networks (2d ed. Prentice Hall 1989)
[0151] Reference 8: Jainsa, Internet Programming (Jamsa Press 1995)
[0152] Reference 9: Comer, Internetworking with TCP/IP, Volumes 1, 2, & 3 (2d ed. Prentice Hall 1995)
[0153] Reference 10: Petzold, Programming Windows 95 (Microsoft 1996)
[0154] Reference 11: Prosise, Programming Windows 95 with MFC (Microsoft Press 1996)
[0155] Reference 12: Chapman, Building Internet Applications with Delphi 2 (Que 1996)
[0156] Reference 13: Schneier, Applied Cryptography (2nd edition John Wiley & Sons 1995)
[0157] Reference 14: Chan, The Java Class Libraries (Addison Wesley 1997)
[0158] Reference 15: Siegel, CORBA Fundamentals and Programming (John Wiley & Sons 1996)
[0159] Reference 16: Lemay, Official Marimba Guide to Castanet (Sams.Net 1997)
[0160] Reference 17: Adkins, Internet Security Professional Reference (New Riders 1996)
[0161] Reference 18: Microsoft Corporation, Windows NT Server Resource Kit (Microsoft Press 1996)
[0162] Reference 19: Russel, Running Windows NT Server (Microsoft Press 1997)
[0163] Reference 20: Lemay et al., Java in 21 Days (Sams.Net 1996)
[0164] Reference 21: Danesh, JavaScript in a Week (Sams.Net 1996)
[0165] Reference 22: Kovel et al., The Lotus Notes Idea Book (Addison Wesley 1996)
[0166] Reference 23: Sun Microsystems, Inc., The JavaBeans 1.0 API Specification (Sun Microsystems 1996) (available at http://java.sun.com beans)
[0167] Reference 24: Sun Microsystems, Inc., The Java 1.1 API Specification (Sun Microsystems 1997) (available at http://java.sun.com/)
[0168] Reference 25: Bell, “Make Java fast: Optimize!,” JavaWorld April 1997 (JavaWorld 1997) (available at http://wwwjavaworld.com/)
[0169] Reference 26: Vanhelsuwe, “How to make Java applets start faster,” JavaWorld December 1996 (JavaWorld 1996) (available at http://wwwjavaworld.com/)
[0170] Although the present invention has been shown and described with respect to preferred embodiments, various changes and modifications, even if not shown or specifically described herein, are deemed to lie within the spirit and scope of the invention and the following claims. Importantly, it should be understood that any specific features or aspects of the embodiments described or illustrated herein are not intended to limit the scope and interpretation of the claims in a manner not explicitly required by the claims.
Claims
What is claimed is:
1. A method of retrieving information from a remotely-located collection of documents for a user of a multi-tasking computer system, wherein the remotely-located collection of documents can be accessed simultaneously by many remote users, the method comprising the acts of:
retrieving a first document over a low-bandwidth connection when the user requests the first document, wherein the first document contains both text and graphics, and wherein the user requests the first document using an input device that allows the user to navigate through documents on a display screen;
displaying the first document on the display screen;
retrieving a second document over the low-bandwidth connection to the collection of documents when the user requests the second document, wherein the second document contains both text and graphics, wherein the user requests the second document using the input device that allows the user to navigate through documents on the display screen, and wherein the second document contains a link to the first document and a link to a third document;
displaying the second document on the display screen by replacing a document previously displayed on the display screen with the second document;
preloading into local storage over the low-bandwidth connection at least a portion of the first document before the user makes another request for the first document by using the input device that allows the user to navigate through documents on the display screen;
preloading into local storage over the low bandwidth connection at least a portion of the third document before the user makes a request for the third document by using the input device that allows the user to navigate through documents on the display screen;
displaying the third document on the display screen when the user requests the third document, wherein the third document is displayed quickly by retrieving from local storage at least a portion of the third document that was preloaded into local storage.
2. The method of claim 1, further comprising the act of:
displaying the first document on the display screen when the user requests the first document, wherein the first document is displayed quickly by retrieving from local storage a version of the first document that was preloaded into local storage.
3. The method of claim 2, further comprising the acts of:
determining if the version of the first document stored in local storage is out-of-date; and
displaying the version of the first document that is stored in local storage.
4. A method of retrieving documents from a remotely-located collection of documents for a user of a multi-tasking computer system, wherein the remotely-located collection of documents can be accessed simultaneously by many remote users, the method comprising the acts of:
retrieving a first document over a low-bandwidth connection when the user requests the first document, wherein the first document contains both text and graphics, and wherein the user requests the first document using an input device that allows the user to navigate through documents on a display screen;
displaying the first document on the display screen;
retrieving a second document over the low-bandwidth connection when the user requests the second document, wherein the second document contains both text and graphics, and wherein the user requests the second document using the input device that allows the user to navigate through documents on the display screen;
displaying the second document on the display screen by replacing the first document previously displayed on the display screen with the second document;
retrieving a third document over the low-bandwidth connection to the collection of documents when the user requests the third document, wherein the third document contains both text and graphics, wherein the user requests the third document using the input device that allows the user to navigate through documents on the display screen, and wherein the third document contains a link to the first document and a link to a fourth document;
displaying the third document on the display screen by replacing the second document previously displayed on the display screen with the third document;
preloading into local storage over the low-bandwidth connection at least a portion of the first document before the user makes another request for the first document by using the input device that allows the user to navigate through documents on the display screen;
preloading into local storage over the low bandwidth connection at least a portion of a fifth document before the user makes a request for the fifth document by using the input device that allows the user to navigate through documents on the display screen, wherein the first document and the fifth document are preloaded simultaneously;
displaying the first document again on the display screen when the user requests the first document, wherein the first document is displayed quickly by retrieving from local storage at least a portion of the first document that was preloaded into local storage;
preloading into local storage over the low bandwidth connection at least a portion of a sixth document before the user makes a request for the sixth document by using the input device that allows the user to navigate through documents on the display screen; and
preloading into local storage over the low bandwidth connection at least a portion of a seventh document before the user makes a request for the seventh document by using the input device that allows the user to navigate through documents on the display screen, wherein the sixth document and the seventh document are preloaded simultaneously.
5. The method of claim 4, wherein the act of displaying the first document again when the user requests the first document includes the acts of:
retrieving a version of the first document that is stored in local storage;
determining if the version of the first document stored in local storage is out-of-date; and
displaying the version of the first document that is stored in local storage.
Patent Citations (113)
| Patent | Date | Inventor | Cited By |
|---|---|---|---|
| US4723211(A) | 1988-02-01 | Barker et al. | Applicant |
| US4730252(A) | 1988-03-01 | Bradshaw | Applicant |
| US4760606(A) | 1988-07-01 | Lesnick et al. | Applicant |
| US4815029(A) | 1989-03-01 | Barker et al. | Applicant |
| US4839853(A) | 1989-06-01 | Deerwester et al. | Applicant |
| US4855725(A) | 1989-08-01 | Fernandez | Applicant |
| US4899292(A) | 1990-02-01 | Montagna | Applicant |
| US4931935(A) | 1990-06-01 | Ohira | Applicant |
| US4945476(A) | 1990-07-01 | Bodick et al. | Applicant |
| US4954969(A) | 1990-09-01 | Tsumura | Applicant |
| US4982344(A) | 1991-01-01 | Jordan | Applicant |
| US4996642(A) | 1991-02-01 | Hey | Applicant |
| US5021989(A) | 1991-06-01 | Fujisawa et al. | Applicant |
| US5062074(A) | 1991-10-01 | Kleinberger | Applicant |
| US5122951(A) | 1992-06-01 | Kamiya | Applicant |
| US5123088(A) | 1992-06-01 | Kasahara et al. | Applicant |
| US5157783(A) | 1992-10-01 | Anderson et al. | Applicant |
| US5206949(A) | 1993-04-01 | Cochran et al. | Applicant |
| US5220648(A) | 1993-06-01 | Sato | Applicant |
| US5235680(A) | 1993-08-01 | Bijnagte | Applicant |
| US5241671(A) | 1993-08-01 | Reed et al. | Applicant |
| US5243149(A) | 1993-09-01 | Comerford et al. | Applicant |
| US5253337(A) | 1993-10-01 | Hirose | Applicant |
| US5255386(A) | 1993-10-01 | Prager | Applicant |
| US5257367(A) | 1993-10-01 | Goodlander | Applicant |
| US5261071(A) | 1993-11-01 | Lyon | Applicant |
| US5265065(A) | 1993-11-01 | Turtle | Applicant |
| US5289569(A) | 1994-02-01 | Taniguchi | Applicant |
| US5295243(A) | 1994-03-01 | Robertson | Applicant |
| US5301109(A) | 1994-04-01 | Landauer et al. | Applicant |
| US5325298(A) | 1994-06-01 | Gallant | Applicant |
| US5341293(A) | 1994-08-01 | Vertelney | Applicant |
| US5345551(A) | 1994-09-01 | Shelley | Applicant |
| US5347632(A) | 1994-09-01 | Filepp et al. | Examiner |
| US5390281(A) | 1995-02-01 | Luciw et al. | Applicant |
| US5392387(A) | 1995-02-01 | Fitzpatrick et al. | Applicant |
| US5404442(A) | 1995-04-01 | Foster | Applicant |
| US5408655(A) | 1995-04-01 | Oren et al. | Applicant |
| US5418948(A) | 1995-05-01 | Turtle | Applicant |
| US5421008(A) | 1995-05-01 | Banning et al. | Applicant |
| US5471575(A) | 1995-11-01 | Giansante | Applicant |
| US5495581(A) | 1996-02-01 | Tsai | Applicant |
| US5511160(A) | 1996-04-01 | Robson | Applicant |
| US5524193(A) | 1996-06-01 | Covington | Applicant |
| US5526520(A) | 1996-06-01 | Krause | Applicant |
| US5535422(A) | 1996-07-01 | Chiang | Applicant |
| US5544352(A) | 1996-08-01 | Egger | Applicant |
| US5572643(A) | 1996-11-01 | Judson | Applicant |
| US5617526(A) | 1997-04-01 | Oran et al. | Applicant |
| US5623679(A) | 1997-04-01 | Rivette et al. | Applicant |
| US5632022(A) | 1997-05-01 | Warren | Applicant |
| US5644686(A) | 1997-07-01 | Hekmatpur | Applicant |
| US5675788(A) | 1997-10-01 | Husick | Applicant |
| US5692107(A) | 1997-11-01 | Simudis | Applicant |
| US5696965(A) | 1997-12-01 | Dedrick | Applicant |
| US5706452(A) | 1998-01-01 | Ivanov | Applicant |
| US5706507(A) | 1998-01-01 | Schloss | Applicant |
| US5714971(A) | 1998-02-01 | Shalit | Applicant |
| US5715445(A) | 1998-02-01 | Wolfe | Examiner |
| US5742284(A) | 1998-04-01 | Duggan | Applicant |
| US5765138(A) | 1998-06-01 | Aycock | Applicant |
| US5768578(A) | 1998-06-01 | Kirk | Applicant |
| US5778398(A) | 1998-07-01 | Nagashima | Applicant |
| US5781189(A) | 1998-07-01 | Holleran | Applicant |
| US5801702(A) | 1998-09-01 | Dolan | Applicant |
| US5802292(A) | 1998-09-01 | Mogul | Applicant |
| US5806077(A) | 1998-09-01 | Wecker | Applicant |
| US5808611(A) | 1998-09-01 | Johnson | Applicant |
| US5822539(A) | 1998-10-01 | van Hoff | Applicant |
| US5826025(A) | 1998-10-01 | Gramlich | Applicant |
| US5826261(A) | 1998-10-01 | Spencer | Applicant |
| US5826267(A) | 1998-10-01 | McMillan | Applicant |
| US5826269(A) | 1998-10-01 | Hussey | Applicant |
| US5835922(A) | 1998-11-01 | Shima | Applicant |
| US5860074(A) | 1999-01-01 | Rowe | Applicant |
| US5864850(A) | 1999-01-01 | Nordman | Applicant |
| US5870552(A) | 1999-02-01 | Dozier | Applicant |
| US5870770(A) | 1999-02-01 | Wolfe | Applicant |
| US5877760(A) | 1999-03-01 | Onda | Applicant |
| US5878421(A) | 1999-03-01 | Ferrel | Applicant |
| US5890172(A) | 1999-03-01 | Borman | Applicant |
| US5893914(A) | 1999-04-01 | Clapp | Applicant |
| US5905492(A) | 1999-05-01 | Straub | Applicant |
| US5913040(A) | 1999-06-01 | Rakavy | Applicant |
| US5915256(A) | 1999-06-01 | Rogers | Applicant |
| US5933811(A) | 1999-08-01 | Angles | Applicant |
| US5946682(A) | 1999-08-01 | Wolfe | Examiner |
| US5948061(A) | 1999-09-01 | Merriman et al. | Applicant |
| US5959621(A) | 1999-09-01 | Nawaz | Applicant |
| US5959632(A) | 1999-09-01 | van Hoff | Applicant |
| US5960409(A) | 1999-09-01 | Wexler | Applicant |
| US5963205(A) | 1999-10-01 | Sotomayor | Applicant |
| USRE36422(E) | 1999-11-01 | Pazel | Applicant |
| US6006252(A) | 1999-12-01 | Wolfe | Applicant |
| US6011537(A) | 2000-01-01 | Slotznick | Applicant |
| US6012053(A) | 2000-01-01 | Pant | Applicant |
| US6023698(A) | 2000-02-01 | Lavey | Applicant |
| US6023726(A) | 2000-02-01 | Saksena | Applicant |
| US6034680(A) | 2000-03-01 | Kessenich | Applicant |
| US6038601(A) | 2000-03-01 | Lambert et al. | Applicant |
| US6094675(A) | 2000-07-01 | Sunaga | Applicant |
| US6138128(A) | 2000-10-01 | Perkowitz | Applicant |
| US6151021(A) | 2000-11-01 | Berquist | Applicant |
| US6151603(A) | 2000-11-01 | Wolfe | Examiner |
| US6216141(B1) | 2001-04-01 | Straub | Applicant |
| US6226655(B1) | 2001-05-01 | Borman | Applicant |
| US6263351(B1) | 2001-07-01 | Wolfe | Applicant |
| US6282548(B1) | 2001-08-01 | Burner | Applicant |
| US6292813(B1) | 2001-09-01 | Wolfe | Applicant |
| US6301576(B1) | 2001-10-01 | Wolfe | Applicant |
| US6321991(B1) | 2001-11-01 | Knowles | Applicant |
| US6336131(B1) | 2002-01-01 | Wolfe | Applicant |
| US6341305(B2) | 2002-01-01 | Wolfe | Applicant |
Non-Patent Literature (96)
- Finnie, “The Browser Push Is On,” PC Magazine, Sep. 9, 1997, pp. 123-128.Applicant
- Dragan, “Advice From The Web,” PC Magazine, Sep. 9, 1997, pp. 133-144.Applicant
- Finnie, “Not Just Browsing,” PC Magazine, Aug. 1997, pp. 45-54.Applicant
- Bannan, “Navigating Made Easy,” PC Magazine, Jul. 1997, p. 81.Applicant
- “And Now, the Webtop,” PC Magazine, Jun. 24, 1997, p. 9.Applicant
- Blight, ““Annotated Reference List Agents,”” IEEE 1997 Conference on Communications, Power and Computing WESCANEX97 Proceedings, May 22, 1997, pp. 7-12.Applicant
- Randal, “Web Central,” PC Magazine, Apr. 22, 1997, p. 65.Applicant
- Clyman, Mendelson, and Nadel, “In Your Face Browsing,” PC Magazine, Apr. 22, 1997, pp. 45-48.Applicant
- Shankar, “Blaze browsing tool packs punch,” Infoworld, Apr. 14, 1997 (available at http://www.infoworld.com/cgi-bin/displayArchives.pl?97-iw01-15.72c.htm).Applicant
- Sirapyan, “Pushing Content Along,” PC Magazine, Apr. 8, 1997, p. 40.Applicant
- Munro, “Internet Filtering Utilities,” PC Magazine, Apr. 8, 1997, pp. 235-240.Applicant
- Mendelson, “Internet Off-line Search Utilities,” PC Magazine, Apr. 8, 1997, pp. 227-232.Applicant
- Mendelson, “Internet Off-line Browsers,” PC Magazine, Apr. 8, 1997, pp. 207-218.Applicant
- Intercast Press Releases, Apr. 7-8, 1997 (from www.intercast.com).Applicant
- Frelechoux, ““An Architecture to Support Personalized Web Applications,”” Apr. 7, 1997 (available at http://www.scope.gmd.de/info/www6/posters/726/poster726.html).Applicant
- Robertson, “A Personalized Web,” Internet World, Apr. 1997, pp. 32-34.Applicant
- Bell, “Make Java Fast: Optimize!,” JavaWorld Apr. 1997 (JavaWorld 1997) (available at http://www.javaworld.com/).Applicant
- Lidsky, “The Web Delivers,” PC Magazine, Feb. 18, 1997, pp. 128-143.Applicant
- Proffit, “Intercast Brings the Web to TV,” PC Magazine, Jan. 21, 1997, pp. 203-204.Applicant
- Isaacs, Inside Dynamic HTML (Microsoft Press 1997).Applicant
- Moeller, ““Caching Software Speeds Browsing,”” PC Week, Dec. 2, 1996, p. 33.Applicant
- Lidsky, “Personal Webcasting,” PC Magazine, Dec. 17, 1996, p. 40.Applicant
- Livingston, “Will Too Many Users Destroy the Internet? I Hardly Think So,” Infoworld, Dec. 9, 1996, p. 35.Applicant
- Sun Microsystems, Inc., The JavaBeans 1.0 API Specification (Sun Microsystems 1996) (available at http://java.sun.com/beans).Applicant
- Singh and Lidsky, “All-Out Search,” PC Magazine, Dec. 3, 1996, pp. 213-249.Applicant
- Vanhelsuwe, “How to Make Ja va A pplets S tart F aster,” Netscape World, Dec. 1996 (from www.netscapeworld.com).Applicant
- Pulver, “A Personal Cast,” Internet World, Dec. 1996, pp. 110-112.Applicant
- Haskin, “Clearing a Path on the Web,” PC Magazine, Nov. 19, 1996, p. 58.Applicant
- Mendelson, “The Finder of Lost Sites,” PC Magazine, Nov. 5, 1996, p. 48.Applicant
- Livingston, “Java-based app speeds Web pages to your browser,” Infoworld, Nov. 4, 1996 (available at http://www.infoworld.com/cgi-bin/displayNew.pl?/livingst/ bl110496.htm).Applicant
- “Internet Performance Products: Peak Net.Jet” (available at http://www.peak-media.com/netjet/netjet.html), Dec. 29, 1996.Applicant
- Levin, “Searching for Meaning,” PC Magazine, Sep. 24, 1996, p. 36.Applicant
- Perenson, “Your Web Surfing Companion,” PC Magazine, Sep. 10, 1996, p. 73.Applicant
- Levin, “New Web Tool Reads Minds,” PC Magazine, Sep. 10, 1996, p. 36.Applicant
- Venditto, “Safe Computing,” Internet World, Sep. 1996, pp. 49-58.Applicant
- Metz, “PC Broadcast News: PointCast Delivers over the Internet,” PC Magazine, Jul. 1996, p. 60.Applicant
- Perenson, “Make a Dash for the Web,” PC Magazine, Jun. 11, 1996, p. 73.Applicant
- Canter, “Internet Search Tools,” PC Magazine, May 14, 1996, pp. 207-210.Applicant
- Venditto, “Search Engine Showdown,” Internet World, May 1996, pp. 79-86.Applicant
- Ayre and Mace, “Internet Access: Just Browsing,” PC Magazine, Mar. 12, 1996, pp. 100-146.Applicant
- Siegel, CORBA Fundamentals and Programming, (John Wiley & Sons 1996).Applicant
- Prosise, Programming Windows 95 with MFC (Microsoft Press 1996).Applicant
- Petzold, Programming Windows 95 (Microsoft 1996).Applicant
- Lemay, Official Marimba Guide to Castnet, (SamsNet 1997).Applicant
- Lemay, Java in 21 Days (SamsNet 1996).Applicant
- Graham, HTML Sourcebook (John Wiley & Sons 1996).Applicant
- Danesh, JavaScript in a Week (Sams.net 1996).Applicant
- Chappell, Understanding ActiveX and OLE, (Microsoft Press 1996).Applicant
- Chapman, Building Internet Applications with Delphi 2 (Que 1996).Applicant
- Cantu, Mastering Delphi 3, (2d ed. Sybex 1996).Applicant
- Campione and Walrath, The Java Tutorial (Addison Wesley 1996).Applicant
- “Blaze Web Performance Pack: xSpeed Technology,” (from http://www.xspeed.com/xspeed.htm), Dec. 30, 1996.Applicant
- Kovel, Quirk, & Gabin, The Lotus Notes Idea Book (Addison-Wesley 1996).Applicant
- Nick Wingfield, “Web-wise apps,” Infoworld, Aug. 28, 1995 pp. 1, 20.Applicant
- Roscheisen, ““Beyond Browsing: Shared Comments, SOAPs, Trails, and Online Communities,”” Computer Networks and ISDN Systems, Apr. 10, 1995.Applicant
- “Netscape's DDE Implementation,” (from www.netscape.com) Mar. 22, 1995.Applicant
- Grunin, “Publish Without Paper,” PC Magazine, Feb. 7, 1995, pp. 110-171.Applicant
- Ayre & Reichard, “The Web Untangled,” PC Magazine, Feb. 7, 1995, pp. 173-196.Applicant
- The End of the Beginning (pamphlet) (1995 LEXIS/NEXIS).Applicant
- Software Products: Prepare to Practice (pamphlet) (1995 LEXIS/NEXIS).Applicant
- Jamsa, Internet Programming (Jamsa Press 1995).Applicant
- Discovering Westlaw: The Essential Guide (4th ed.) (1995 West Publishing Company).Applicant
- Denning, OLE Controls Inside Out (Microsoft 1995).Applicant
- Brown, Using Netscape 2, pp. 773-786 (Que 1995).Applicant
- Brockschmidt, Inside OLE (2d ed. Microsoft Press 1995).Applicant
- “.More” Product Literature (two pages), (©1995 LEXIS/NEXIS).Applicant
- Joel Snyder, “Taming the Internet,” MacWorld, Dec. 1994, pp. 115-117.Applicant
- Mark Brownstein, “Fast Drives, Tiny Packages,” PC/Computing, Nov. 1994, pp. 140-141.Applicant
- Using Mosaic (Que Corporation 1994), pp. 31-44 & 80-85.Applicant
- Shepard's United States Citations: CD-ROM Edition, © 1994 McGraw-Hill, Inc.Applicant
- PatentWorks Workbench User's Guide, Waverly Systems, Inc., pp. 1-6, 67-95, and Quick Reference Card, ©1994 Waverly Systems, Inc.Applicant
- Freestyle Quick Reference (pamphlet) (1995 LEXIS/NEXIS).Applicant
- Comer, Internetworking with TCP/IP, vols. 1, 2 & 3 (Prentice Hall 1994-1997).Applicant
- Questions & Answers (to be used with “How to Shepardize”) (1993 McGraw-Hill, Inc.).Applicant
- How to Shepardize, © 1993 McGraw-Hill.Applicant
- Foss, “Tools for Reading and Browsing Hypertext,” Information Processing & Management, vol. 25, No. 4, pp. 405-418, 1988.Applicant
- Tanenbaum, Computer Networks (2d ed. Prentice Hall 1981).Applicant
- Wolfe, U.S. patent application Ser. No. 09/620,651, filed Jul. 20, 2000, Wolfe, now abandoned.Applicant
- Wolfe, U.S. patent application Ser. No. 09/083,382, filed May 22, 1998, now abandoned.Applicant
- Wolfe, U.S. patent application Ser. No. 60/047,554, filed May 22, 1997, now expired.Applicant
- Wolfe, U.S. patent application Ser. No. 08/918,912, filed Aug. 27, 1997, now U.S. Pat. No. 5,946,682, Wolfe.Applicant
- Wolfe, U.S. patent application Ser. No. 08/474,921, filed Jun. 7, 1995, now U.S. Pat. No. 5,715,445.Applicant
- Wolfe, U.S. patent application Ser. No. s/n 08/300,343, filed Sep. 2, 1994, now abandoned.Applicant
- Roberts, “Controlling Internet Explorer 4.0 with Brower Helper Objects,” Microsoft Interactive Developer, May 1998, p. 66.Applicant
- Hannon, “New Window on Web Ads,” PC Week, Feb. 2, 1998.Applicant
- Netscape Communicator Plug-in Guide (Netscape Communications Corporation Jan. 1998).Applicant
- Bremser, “HTML Workshop: Making Frames Fit,” Internet World, Sep. 1997, pp. 90-92.Applicant
- Rapoza, “Alexa's Theory of Relativity,” PC Week, Aug. 18, 1997, p. 42.Applicant
- “Internet 101: Web Rings,” CNET.COM, July 17, 1997 (www.cnet.com).Applicant
- Bederson, ““Pad plus plus: A Zoomable Graphical Interface System,”” Proceedings of the Conference on Human Factors in Computing Systems, May 1995, pp. 23-24.Applicant
- Andrews, ““Hyper-G and Harmony: Towards the Next Generation of Networked Information Technology,”” Proceedings of the Conference on Human Factors in Computing Systems, May 1995, pp. 33-34.Applicant
- Huser, ““Knowledge-based Edidting and Visualization for Hypermedia Encyclopedias,”” Communications of the Association of Computing Machinery, vol. 38, Apr. 1995, pp. 49-51.Applicant
- Fowler, ““Experience with the Virtual Notebook System: Abstraction in Hypertext,”” Transcending Boundaries, Proceedings of the Conference on Computer Supported Cooperative Work, Oct. 1994, pp. 133-143.Applicant
- Robertson, ““The Hypermedia Authoring Research Toolkit (Hart),”” Proceedings of European Conference on Hypermedia Technology, Sep. 1994, pp. 177-185.Applicant
- Bieber, ““Backtracking in a Multiple-Window Hypertext Enviroment,”” ACM European Conference on Hypermedia Technology, Sep. 1994, pp. 158-166.Applicant
- Instone, ““Empirically-based Redesign of a Hypertext Encyclopedia,”” Conference Proceedings on Human Factors in Computing Systems, Apr. 1993, pp. 500-506.Applicant