Google Inc.

Rennie Glen Software, LLC

Jeffrey Glen Rennie

Othman Laraki

Paul Thomas Buchheit

Cosmos Nicolaou

Hanping Feng

Eric Russell Fredricksen

Bjorn Marius Aamodt Eriksen

Bjorn Marius Aamodt Erikson

Denis Lee Severson

Before preloading a document to a client device, a server computer gets a client cache map associated with the client device. The client cache map has a matching entry for each document cached by the client device's cache. The server computer first checks if the document to be preloaded is already in the client device's cache by looking up the client cache map. If the document is cached, the server computer then checks whether the cached document's content is still fresh. As a result, the server computer preloads the document to the client device if the document is not cached or if the cached document's content is stale.

Systems and methods for client cache awareness

Documents are preloaded from a server to a client device before the client device submits a request for the preloaded documents. The server predicts which documents to preload based on past user browsing activities at the client device and document layouts. At the client device, specific graphical features may be applied to the links to the preloaded documents such that a user can easily tell which document link is associated with the preloaded documents.

Systems and methods of efficiently preloading documents to client devices

A client assistant, sometimes called a browser helper, runs on a client computer. The client assistant monitors a user's browsing activities and infers one or more next documents that are most likely to be requested by the user. The client assistant attempts to locate a fresh copy of the inferred next document within a client cache. If a fresh copy of the inferred document is not found in the client cache, the client assistant submits a document download request to a document server.

Accelerating user interfaces by predicting user actions

A method for increasing the tamper resistance of a computer software application comprises four steps. In the first step, a datum in the application to protect from tampering is chosen. In the second step, a location in memory into which the datum will be loaded when the application is executed is calculated. In the third step, user-purpose code to modify is chosen. In the fourth step, the chosen user-purpose code is modified so that, when executed, it reads a value from the memory location and uses it in useful calculation.

Growing community of inventors

Mountain View, CA, United States of America

Jeffrey Glen Rennie