Google Inc.

Matthew James Bolohan

Robert John Kroeger

Andrew Alexander Grieve

Derek Jason Phillips

Ryan James Fioravanti

Aleksandr Kennberg

Phillip Neal Sharp

David Edward Stewart

Neil Thomas

Alex Nicolaou

Bikin Chiu

Xander Pollock

Nathan Bullock

Raymond Wainman

Daniel George Calvert

Aakash Sahney

A computing device is described that receives an electronic message encoded with first rendering instructions and second rendering instructions. The first rendering instructions are accelerated mobile pages instructions and the second rendering instructions are at least one of plain text or hypertext markup language instructions. The computing device generates a rendering of the electronic message by at least: rendering the second rendering instructions, while refraining from rendering the first rendering instructions, in response to determining that the first rendering instructions are not valid accelerated mobile pages instructions. The computing device outputs, using a display, the rendering of the electronic message.

Secure electronic messaging with dynamic content

The subject matter of this disclosure can be implemented in, among other things, a device that includes processors, a data repository, and a table version module configured to create a first version of a database within the data repository using a first version of a database schema that defines a set of tables for the database, and receive a result that is responsive to a command, such that when the result indicates a success condition, execution of the command allows access to data contained in the database and verification of the database schema version, wherein the result does not include database schema version information. The device further includes means for executing the command to access the data, wherein the command includes one or more encoded table names, and wherein each of the encoded table names included in the command is generated based on at least a database schema version identifier.

Encoding a schema version in table names

A method throttles display of electronic messages. The process displays a list of entries in an email application. The list of entries includes a first electronic message, a first message cluster, and a second message cluster. The process detects the occurrence of a cluster display trigger event for the first message cluster. The trigger event is one of: detection of passage of a predetermined amount of time since refreshing display of the first message cluster, an occurrence of a particular time of day, an occurrence of a predetermined date, or receipt by the first message cluster of a predefined number of new electronic messages since previously refreshing the display of the list. In response to the detected trigger event, the process refreshes the display of the list of entries, including re-ranking the first message cluster within the list of entries. This changes the relative position of the first message cluster.

Systems and methods for throttling display of electronic messages

In general, techniques for passing data from a native component to a web component of a hybrid application without reflowing the top-level document are described. The native component is located within a user space of a computing device and intercepts a request for a resource issued by the web component of the application. The native component provides access to an interface not otherwise accessible by the web component. If the request for the resource is a request for data through the interface, the native component enqueues the request in a request pool, receives the data responsive to the request through the interface, forms a response to the request using the data, dequeues the request after receiving the data, and sending, the response to the web component. If not, the native component grants permission to the web component to issue the request to a remote server.

Hybrid application message passing

A computing device has one or more processors and memory storing programs executed by the one or more processors. The computing device initializes a main application on a first thread. The main application has a first synchronous connection with a target application. After the main application performs one or more operations at the target application through the first synchronous connection, the computing device initializes an assistant process on a second thread. The assistant process has a second synchronous connection with the target application and an asynchronous connection with the main application. After receiving a request from the main application through the asynchronous connection, the assistant process performs one or more operations at the target application through the second synchronous connection.

System and method for reducing startup cost of a software application

Techniques are described herein that provide for inter-domain communications with one or more shared worker applications. A parent web application associated with a first domain may create a child web application associated with a second domain different than the first domain. The child web application may determine whether a shared worker associated with the second domain is operating. The shared worker acquires information associated with the second domain in response to one or more requests, and stores acquired information associated with the second domain in a memory of the local computing device. The parent web application may request, via the child web application, information associated with the second domain from the shared worker. In response to the request, the parent web application may receive, from the shared worker, information associated with the second domain stored in the memory of the local computing device.

Cross-domain communications with a shared worker application

A background page script is executing on a device. A plurality of webpages are executing on the device. The plurality of webpages register with the background page script. An action generated by one of the plurality of webpages is cached in a database. In response to a determination that the device is in an online state and that the one of the plurality of webpages is no longer registered, the background page script retrieves the action from the database and transmits the action.

System and method for synchronization of actions in the background of an application

A request to update a list of conversations is sent to a server. At least a portion of each conversation in the list of conversations is stored on the client. A plurality of updates is received form the server. The plurality of updates includes messages corresponding to respective conversations in the list of conversations.

Mechanism for message prefetching in an intermittently connected offline-capable mobile web application

A method includes rendering content to provide rendered content including a first content segment and a second content segment, wherein the second content segment includes an indicator of computing device activity; outputting a first view of the rendered content for presentation at a display device, and receiving, at the one or more processors, event information. In response to the event information, the method includes applying at least one hardware accelerated transform to define a second view of the rendered content, where the second content segment, but not the first content segment, is viewable in the second view of the rendered content when the rendered content is presented at the display device, modifying the first content segment, and applying at least one hardware accelerated transform to define a third view of the rendered content subsequent to modifying the first content segment.

Accelerating view transitions

Techniques are described herein that provide a web application that incorporates one or more shared worker applications. In one example, a shared worker application as described herein may receive a first request for first information for a first web application, acquire the first information in response to the request, and store at least a portion of the first information in a memory of a local communications device. The shared worker may further receive a second request for second information for a second web application. The shared worker may determine whether at least a portion of the first information stored in the memory of the local communications device will satisfy the second request for the second information. The shared worker may provide, from the local memory to the second web application, at least the portion of the first information in response to the second request.

Shared worker application

In general, techniques for passing data from a native component of an application to a web component of the application without reflowing the top-level document are described. In one example, a web component of an application loads a main document that includes at least two separate frames that each causes the web component to issue an application-layer request specifying a uniform resource identifier (URI). One of the frames causes the web component to issue an application-layer request that specifies a special native request URI. A native component of the application monitors application-layer requests issued by the web component of the application and snoops the URIs specified therein. When the native component identifies an application-layer request specifying a special native request URI, the native component stores a reference to the open application-layer request. Subsequently, the native component may pass a message to the web component by responding to the application-layer request.

Systems and methods for managing database transactions communicated from a browser-based software application to a database by a database management system in order to avoid or ameliorate transaction latency. According to one embodiment, the system or method comprises foreground and background processes, each generating database transactions. The foreground processes can submit an unlimited number of transactions to the database while background processes can only submit a limited, predetermined number of transactions to the database. To accomplish this, the background processes are associated with an in-memory queue of transactions that are then submitted to the database in a quantity no greater than the predetermined number. As a result, the database transactions sent by the foreground process will not have to wait behind more than the predetermined number of background transactions, thereby resulting in lower latency and avoiding or ameliorating delays to the user.

Growing community of inventors

Kitchener, Canada

Matthew James Bolohan