LIVE UPDATING OF A SHARED PLUGIN REGISTRY WITH NO SERVICE LOSS FOR ACTIVE USERS

• US 20170139704A1
• Filed: 01/31/2017
• Published: 05/18/2017
• Est. Priority Date: 09/26/2014
• Status: Active Grant

• Current Assignee: Oracle International Corporation (Oracle Corporation)
• Original Assignee: Oracle International Corporation (Oracle Corporation)
• Inventors: Katkere, Arun Lakshminarayan, Lagerblad, Bo Jonas Birger
• Granted Patent: US 10,095,510 B2
• Time in Patent Office: Days
• CPC Class Codes: G06F 8/61 Installation
• CPC Class Codes: G06F 8/65 Updates security arrangements therefor G06F21/57
• CPC Class Codes: G06F 8/656 while running
• CPC Class Codes: G06F 8/658 Incremental updates; Differential updates
• CPC Class Codes: G06F 8/71 Version control security arrangements therefor G06F21/57; Configuration management
• CPC Class Codes: G06F 9/44526 Plug-ins; Add-ons

Abstract

Embodiments can enable the uploading of a newer version of a plugin package to a plugin service without affecting an existing user session that is using an older version of the plugin package. When a new user session begins, the plugin service can monitor one or more plugin packages and the versions used during the new user session. Throughout the user session, the plugin service continues to make the plugin packages available to the user regardless of newer versions being uploaded to the plugin service. In the meantime, multiple clients with different user sessions may be using different and possibly newer versions of the plugin packages at the same time. The plugin service can remove an older version of a plugin package when it determines that there are no longer any active user sessions utilizing the older version of the plugin package.

Claims

1. A method comprising:

providing, by one or more processors, a shared plugin registry, wherein the shared plugin registry includes at least a first version of a plugin package;

detecting, by the one or more processors, a second version of the plugin package in the shared plugin registry, wherein the second version of the plugin package is deployed to replace the first version of the plugin package;

determining, by the one or more processors, a reference count associated with the first version of the plugin package, wherein the reference count indicates a number of active user session associated with the first plugin package; and

maintaining, by the one or more processors, the first version of the plugin package while the reference count indicates at least one active user session is currently using the first version of the plugin package while concurrently providing the second version of the plugin package to a first new user session.

2. The method of claim 1, further comprising:

receiving, by the one or more processors, an indication of a second new user session; and

enabling, by the one or more processors, selection of a plugin package for the second new user session, wherein the plugin package is selected from one of;

the first version of the plugin package and the second version of the plugin package.

3. The method of claim 1, further comprising:

generating, by the one or more processors, a snapshot of each plugin package used by a user session;

incrementing, by the one or more processors, the reference count for each plugin package in the generated snapshot, wherein each plugin package in the snapshot is preserved while the user session is active without preventing newer versions of each plugin package from being added to the shared plugin registry.

4. The method of claim 3, wherein:

the snapshot stores timestamps associated with each plugin package used by the user session; and

access to each plugin package throughout the user session is assured by using the stored timestamps to prevent a plugin package from being replaced by a newer version of the plugin package that is added to the shared plugin registry at a later date.

5. The method of claim 1, further comprising:

updating, by the one or more processors, the reference count for each plugin package in the shared plugin registry by decrementing the reference count associated with a plugin package when a user session associated with the plugin package ends, and incrementing the reference count when a user session associated with the plugin package begins; and

removing, by the one or more processors, a plugin package when;

the reference count of the plugin package is zero, and

a newer version of the plugin package exists in the shared plugin registry.

6. The method of claim 1, wherein:

each plugin package in the shared plugin registry include a plurality of components, wherein the first version of the plugin package and second version of the plugin package have at least one component in common; and

the first version of the plugin package includes an older version of the component and the second version of the plugin package includes a newer version of the component.

7. The method of claim 1, further comprising automatically removing, by the one or more processors, the first version of the plugin package when the reference count associated with the first version of the plugin package is zero.

8. A system comprising:

one or more processors; and

memory coupled to the one or more processors, the memory encoded with a set of instructions configured to perform a process comprising;

providing a shared plugin registry, wherein the shared plugin registry includes at least a first version of a plugin package;

detecting a second version of the plugin package in the shared plugin registry, wherein the second version of the plugin package is deployed to replace the first version of the plugin package;

determining a reference count associated with the first version of the plugin package, wherein the reference count indicates a number of active user sessions associated with the first plugin package; and

maintaining the first version of the plugin package while the reference count indicates at least one active user session is currently using the first version of the plugin package while concurrently providing the second version of the plugin package to a first new user session.

9. The system of claim 8, further comprising:

receiving an indication of a second new user session; and

enabling selection of a plugin package for the second new user session, wherein the plugin package is selected from one of;

the first version of the plugin package and the second version of the plugin package.

10. The system of claim 8, further comprising:

generating a snapshot of each plugin packages used by a user session;

incrementing the reference count for each plugin package in the generated snapshot, wherein each plugin package in the snapshot is preserved while the user session is active without preventing newer versions of each plugin package from being added to the shared plugin registry.

11. The system of claim 10, wherein:

the snapshot stores timestamps associated with the one or more plugin packages used by the user session; and

access to each plugin package throughout the user session is assured by using the timestamp to prevent a plugin package from being replaced by a newer version of the plugin package added to the shared pluginregistry at a later date.

12. The system of claim 8, further comprising:

updating the reference count for each plugin package in the shared plugin registry by decrementing the reference count associated with a plugin package when a user session ends, and incrementing the reference count when a user session associated with the plugin package begins; and

removing a plugin package when;

the reference count of the plugin package is zero, and

a newer version of the plugin package exists in the shared plugin registry.

13. The system of claim 8, wherein:

the plugin package in the shared plugin registry includes a plurality of components, wherein the first version of the plugin package and second version of the plugin package have at least one component in common; and

the first version of the plugin package includes an older version of the component and the second version of the plugin package includes a newer version of the component.

14. The system of claim 8, further comprising:

automatically removing the first version of the plugin package when the reference count associated with the first version of the plugin package is zero.

15. A non-transitory computer readable storage medium storing instructions that, when executed by one or more processors of a first computing device, cause the first computing device to perform operations comprising:

providing a shared plugin registry, wherein the shared plugin registry i at least a first version of a plugin package;

detecting a second version of the plugin package in the shared plugin registry, wherein the second version of the plugin package is deployed to replace the first version of the plugin package;

determining a reference count associated with the first version of the plugin package, wherein the reference count indicates a number of active user sessions associated with the first plugin package; and

maintaining the first version of the plugin package while the reference count indicates at least one active user session is currently using the first version of the plugin package while concurrently providing the second version of the plugin package to a first new user session.

16. The medium of claim 15, further comprising:

receiving an indication of a second new user session; and

enabling selection of a plugin package for the second new user session, wherein the plugin package is selected from one of;

the first version of the plugin package and the second version of the plugin package.

17. The medium of claim 15, further comprising:

generating a snapshot of each plugin packages used by a user session;

incrementing the reference count for each plugin package in the generated snapshot, wherein each plugin package in the snapshot is preserved while the user session is active without preventing newer versions of each plugin package from being added to the shared plugin registry.

18. The medium of claim 17, wherein:

the snapshot stores timestamps associated with the one or more plugin packages used by the user session; and

access to each plugin package throughout the user session is assured by using the timestamp to prevent a plugin package from being replaced by a newer version of the plugin package added to the shared plugin registry at a later date.

19. The medium of claim 15, further comprising:

updating the reference count for each plugin package in the shared plugin registry by decrementing the reference count associated with a plugin package when a user session ends, and incrementing the reference count when a user session associated with the plugin package begins; and

removing a plugin package when;

the reference count of the plugin package is zero, and

a newer version of the plugin package exists in the shared plugin registry.

20. The medium of claim 15, wherein:

the plugin package in the shared plugin registry includes a plurality of components, wherein the first version of the plugin package and second version of the plugin package have at least one component in common; and

the first version of the plugin package includes an older version of the component and the second version of the plugin package includes a newer version of the component.