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

• US 20160092204A1
• Filed: 09/25/2015
• Published: 03/31/2016
• Est. Priority Date: 09/26/2014
• Status: Active Grant

• Current Assignee: Oracle International Corporation (Oracle Corporation)
• Original Assignee: Oracle International Corporation (Oracle Corporation)
• Inventors: Lagerblad, Bo Jonas Birger, Katkere, Arun Lakshminarayn
• Granted Patent: US 9,575,744 B2
• Time in Patent Office: Days
• US Class Current: 1/1
• 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:

uploading a first version of a plugin package to a shared plugin registry, the first version of the plugin package having one or more components;

uploading a second version of the plugin package to the shared plugin registry, wherein the second version of the plugin package has been deployed to replace the first version of the plugin package;

determining a reference count associated with the first version of the plugin package, the reference count being indicative of whether there are one or more active user sessions associated with the first version of the plugin package; and

maintaining, by one or more processors, the first version of the plugin package and the second version of the plugin package in the shared plugin registry when the reference count associated with the first version of the plugin package is not zero.

2. The method of claim 1, further comprising:

receiving an indication that a user session has started after the first version of the plugin package has been uploaded to the shared plugin registry; and

increasing the reference count associated with the first version of the plugin package upon receiving the indication that the user session has started,

wherein the first version of the plugin package is continued to be made available to the user session after the second version of the plugin package is uploaded.

3. The method of claim 2, further comprising:

receiving an indication that another user session has started after the second version of the plugin package has been uploaded to the shared plugin registry; and

providing the second version of the plugin package to the other user session,

wherein the first version of the plugin package is being used in the user session concurrently as the second version of the plugin package in the other user session.

4. The method of claim 2, further comprising:

decrementing the reference count associated with the first version of the plugin package when the user session ends.

5. The method of claim 1, wherein the second version of the plugin package includes a same component from the first version of the plugin package, the same component having the same version number.

6. The method of claim 1, wherein the first version of the plugin package includes a first version of a component and the second version of the plugin package includes a second version of the component.

7. The method of claim 1, further comprising:

when the reference count associated with the first version of the plugin package is zero;

determining whether the first version of the plugin package is the latest version of the plugin package; and

marking the first version of the plugin package for removal from the shared plugin registry if the first version of the plugin package is not the latest version of the plugin package.

8. The method of claim 1, further comprising:

receiving an indication that a new user session has started after the second version of the plugin package has been uploaded to the shared plugin registry;

enabling use of the second version of the plugin package during the new user session instead of the first version; and

increasing a reference count for the second version of the plugin package.

9. The method of claim 8, further comprising:

storing information identifying one or more plugin packages used during the new user session;

storing one or more timestamps associated with the one or more plugin packages, each timestamp identifying a time at which each of the plugin packages was provided for the new user session; and

enabling access to the same one or more plugin packages throughout a duration of the new user session regardless of one or more additional plugin packages uploaded to the shared plugin registry at a later time to the times identified by the one or more timestamps, the one or more additional plugin packages including one or more newer versions of the one or more plugin packages.

10. The method of claim 1, further comprising:

automatically removing the first version of the package when the reference count associated with the first version of the package goes down to zero.

11. 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;

uploading a first version of a plugin package to a shared plugin registry, the first version of the plugin package having one or more components;

uploading a second version of the plugin package to the shared plugin registry, wherein the second version of the plugin package has been deployed to replace

the first version of the plugin package;

determining a reference count associated with the first version of the plugin package, the reference count being indicative of whether there are one or more active user sessions associated with the first version of the plugin package; and

maintaining, by the one or more processors, the first version of the plugin package and the second version of the plugin package in the shared plugin registry when the reference count associated with the first version of the plugin package is not zero.

12. The system of claim 11, wherein the set of instructions are further configured to perform the process comprising:

receiving an indication that a user session has started after the first version of the plugin package has been uploaded to the shared plugin registry; and

increasing the reference count associated with the first version of the plugin package upon receiving the indication that the user session has started,

wherein the first version of the plugin package is continued to be made available to the user session after the second version of the plugin package is uploaded.

13. The system of claim 12, wherein the set of instructions are further configured to perform the process comprising:

receiving an indication that another user session has started after the second version of the plugin package has been uploaded to the shared plugin registry; and

providing the second version of the plugin package to the other user session,

wherein the first version of the plugin package is being used in the user session concurrently as the second version of the plugin package in the other user session.

14. The system of claim 12, wherein the set of instructions are further configured to perform the process comprising:

decrementing the reference count associated with the first version of the plugin package when the user session ends.

15. The system of claim 11, wherein the second version of the plugin package includes a same component from the first version of the plugin package, the same component having the same version number.

16. 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:

uploading a first version of a plugin package to a shared plugin registry, the first version of the plugin package having one or more components;

uploading a second version of the plugin package to the shared plugin registry, wherein the second version of the plugin package has been deployed to replace the first version of the plugin package;

determining a reference count associated with the first version of the plugin package, the reference count being indicative of whether there are one or more active user sessions associated with the first version of the plugin package; and

maintaining, by the one or more processors, the first version of the plugin package and the second version of the plugin package in the shared plugin registry when the reference count associated with the first version of the plugin package is not zero.

17. The computer readable storage medium of claim 16, wherein the instructions further cause the first computing device to perform operations comprising:

receiving an indication that a user session has started after the first version of the plugin package has been uploaded to the shared plugin registry; and

increasing the reference count associated with the first version of the plugin package upon receiving the indication that the user session has started,

wherein the first version of the plugin package is continued to be made available to the user session after the second version of the plugin package is uploaded.

18. The computer readable storage medium of claim 17, wherein the instructions further cause the first computing device to perform operations comprising:

receiving an indication that another user session has started after the second version of the plugin package has been uploaded to the shared plugin registry; and

providing the second version of the plugin package to the other user session,

wherein the first version of the plugin package is being used in the user session concurrently as the second version of the plugin package in the other user session.

19. The computer readable storage medium of claim 17, wherein the instructions further cause the first computing device to perform operations comprising:

decrementing the reference count associated with the first version of the plugin package when the user session ends.

20. The computer readable storage medium of claim 16, wherein the second version of the plugin package includes a same component from the first version of the plugin package, the same component having the same version number.