Sharing a process in a web client
First Claim
1. A machine-implemented method, comprising:
- determining whether a session associated with a first user interface is also associated with a second user interface, wherein the first user interface and the second user interface are different and provided by a same instance of a client application;
determining a security mode of the first user interface and a security mode of the second user interface, wherein the security modes of the first user interface and the second user interface indicate one or more operations that are allowed to be performed by the first user interface and the second user interface, respectively, on a computing device running the client application;
determining whether the security mode of the first user interface matches the security mode of the second user interface;
in response to the session being determined to be associated with the first user interface and the second user interface and the security mode of the first user interface being determined to match the security mode of the second user interface, sharing a first process between the first user interface and the second user interface to access a shared resource for the first user interface or the second user interface, wherein the shared resource is a local data store and the first process performs one or more operations on the local data store; and
in response to the security mode of the first user interface being determined not to match the security mode of the second user interface, instantiating a second process for the second user interface to access a second resource different from the shared resource without access to the shared resource.
2 Assignments
0 Petitions
Accused Products
Abstract
Configurations for sharing an instance of an executing process for a plug-in based on a session and a cookie data store associated with the session are disclosed. A cookie data store can be associated with a tab running in a corresponding security mode. By way of example, instead of initiating a new process for the plug-in in a new tab, the subject technology can first determine whether a previous tab is running an instance of a plug-in process. If this is the case, the subject technology can then determine whether the previous tab is running in the same security mode (e.g., protected or unprotected) as the new tab. The subject technology then shares the existing plug-in process in the previous tab without instantiating a new plug-in process in the new tab.
34 Citations
19 Claims
-
1. A machine-implemented method, comprising:
-
determining whether a session associated with a first user interface is also associated with a second user interface, wherein the first user interface and the second user interface are different and provided by a same instance of a client application; determining a security mode of the first user interface and a security mode of the second user interface, wherein the security modes of the first user interface and the second user interface indicate one or more operations that are allowed to be performed by the first user interface and the second user interface, respectively, on a computing device running the client application; determining whether the security mode of the first user interface matches the security mode of the second user interface; in response to the session being determined to be associated with the first user interface and the second user interface and the security mode of the first user interface being determined to match the security mode of the second user interface, sharing a first process between the first user interface and the second user interface to access a shared resource for the first user interface or the second user interface, wherein the shared resource is a local data store and the first process performs one or more operations on the local data store; and in response to the security mode of the first user interface being determined not to match the security mode of the second user interface, instantiating a second process for the second user interface to access a second resource different from the shared resource without access to the shared resource. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8, 9)
-
-
10. A system, comprising:
-
a non-transitory memory medium comprising instructions stored thereon; and one or more circuits for executing instructions for system operations, wherein the instructions, when executed, cause the circuits to perform operations comprising; determining whether a session associated with a first user interface is also associated with a second user interface, wherein the first user interface and the second user interface are different and provided by a same instance of a client application; determining a security mode of the first user interface and a security mode of the second user interface, wherein the security modes of the first user interface and the second user interface indicate one or more operations that are allowed to be performed by the first user interface and the second user interface, respectively, on a computing device running the client application; determining whether the security mode of the first user interface matches the security mode of the second user interface; in response to the session being determined to be associated with the first user interface and the second user interface and the security mode of the first user interface being determined to match the security mode of the second user interface, sharing a first process between the first user interface and the second user interface to access a shared resource for the first user interface or the second user interface, wherein the shared resource is a local data store and the first process performs one or more operations on the local data store; and in response to the security mode of the first user interface being determined not to match the security mode of the second user interface, instantiating a second process for the second user interface to access a second resource different from the shared resource without access to the shared resource. - View Dependent Claims (11, 12, 13, 14, 15, 16, 17, 18)
-
-
19. A non-transitory machine-readable medium comprising instructions stored therein, which when executed by a machine, cause the machine to perform operations comprising:
-
determining whether a session associated with a first user interface is also associated with a second user interface, wherein the first user interface and the second user interface are different and provided by a same instance of a client application; determining a security mode of the first user interface and a security mode of the second user interface, wherein the security modes of the first user interface and the second user interface indicate one or more operations that are allowed to be performed by the first user interface and the second user interface, respectively, on a computing device running the client application; determining whether the security mode of the first user interface matches the security mode of the second user interface; in response to the session being determined to be associated with the first user interface and the second user interface and the security mode of the first user interface being determined to match the security mode of the second user interface, sharing a first process between the first user interface and the second user interface to access a shared resource for the first user interface or the second user interface, wherein the shared resource is a local data store and the first process performs one or more operations on the local data store; and in response to the security mode of the first user interface being determined not to match the security mode of the second user interface, instantiating a second process for the second user interface to access a second resource different from the shared resource without access to the shared resource.
-
Specification