Abstract:
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.
Abstract:
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.
Abstract:
The techniques of this disclosure are directed to a shared worker application configured to create one or more instantiations and/or to locally synchronize status of one or more sub-component instantiations for one or more web applications. In one example, a shared worker of a browser facilitates creation of sub-component instantiations, by acquiring software defining the sub-component from a memory of a computing device on which the browser is operating, or via a network, and providing the software local to the computing device for execution to create the instantiation of the sub-component. In another example, a shared worker of a browser as described herein facilitates status updates for multiple sub-component instantiations local to a computing device upon which a browser is operating.
Abstract:
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.
Abstract:
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.
Abstract:
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.
Abstract:
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.
Abstract:
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.
Abstract:
Embodiments relate to methods, devices, and computer-implemented methods for determining if an email attachment to be transmitted by an application on the mobile computing device to another computing device on a first data channel exceeds a predetermined size threshold; determining if the email attachment is independent of other active email attachment requests on the first data channel; providing the email attachment over the first data channel if the size is determined not to exceed the predetermined size threshold; providing the email attachment over the first data channel if the email attachment is determined to be dependent of the other active email attachment, requests; and providing the email attachment over a second data channel different than the first data channel if the size is determined to be above the predetermined size threshold and is independent of the other active email attachment requests.
Abstract:
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.