Out of Band Services Updates

• US 20130332917A1
• Filed: 06/08/2012
• Published: 12/12/2013
• Est. Priority Date: 06/08/2012
• Status: Active Grant

• Current Assignee: Adobe Inc.
• Original Assignee: Adobe Systems Incorporated (Adobe Inc.)
• Inventors: Gaither, Shawn A., Swineford, Randy L.
• Granted Patent: US 8,972,969 B2
• Time in Patent Office: Days
• US Class Current: 717/170
• CPC Class Codes: G06F 8/656 while running

Abstract

Out of band component updating may include receiving a data structure that includes information regarding a component of an application. It may further include determining, from the data structure, that an updated version of the component is available. Out of band component updating may also include storing the updated component in a local data store. It may additionally include, during execution of the application and without shutting down the application, updating the component with the stored updated version of the component. Updating the component may include loading the updated version of the component in a time that is substantially similar to that of a time to load a previous version of the component.

Claims

1. A method, comprising:

an update module, executing in an application, receiving a data structure that includes information regarding a component of the application;

the update module determining, from the data structure, that an updated version of the component is available;

the update module storing the updated version of the component in a local data store; and

during execution of the application and without shutting down the application, the update module updating the component with the stored updated version of the component.

2. The method of claim 1, wherein said updating is performed in response to an occurrence of an event relating to the component.

3. The method of claim 2, wherein the event is defined in the data structure as part of the information regarding the component of the application.

4. The method of claim 1, further comprising, prior to said updating:

the update module generating a prompt that the updated component is available for substantially immediate use; and

the update module receiving an input to the prompt indicating to update the component.

5. The method of claim 1, wherein the data structure is received from a secure location of an operating system.

6. The method of claim 1, wherein the information from the data structure regarding the component includes an indication of the updated version of the component, wherein said determining that an update is available is based on a comparison of the indication of the updated version of the component with an indication of a loaded version of the component, wherein the updated version is different from the loaded version.

7. The method of claim 1, wherein the component is a platform-independent component such that the component is usable in a first platform and in a second platform, and wherein the application is platform dependent.

8. The method of claim 1, wherein said updating the component includes loading the updated version of the component from a location in the local data store that is different from a location in the local data store storing a previous version of the component, wherein a time to perform said loading the updated version of the component is substantially similar to a time to perform reading the previous version of the component.

9. The method of claim 1, wherein the data structure includes a list of a location and a hash value of the component.

10. The method of claim 1, wherein the component is a plug-in implemented, at least partially, in a platform-independent scripting language.

11. The method of claim 1, wherein the update is a single, secure compressed file.

12. The method of claim 1, wherein storing the update in a local data store includes:

storing the updated version of the component in a temporary data store;

validating the stored updated version of the component; and

storing the validated stored updated version of the component in the local data store, wherein the local data store is a user-specific local data store.

13. A non-transitory computer-readable storage medium storing program instructions, wherein the program instructions are computer-executable to implement:

receiving a data structure that includes information regarding a component of an application;

determining, from the data structure, that an updated version of the component is available;

storing the updated version of the component in a local data store; and

during execution of the application and without the application shutting down, updating the component with the stored updated version of the component;

wherein a time to perform said updating the component with the stored version of the component is substantially similar to a time to perform reading a previous version of the component.

14. The non-transitory computer-readable storage medium of claim 13, wherein said updating is performed in response to an occurrence of an event.

15. The non-transitory computer-readable storage medium of claim 13, wherein the information from the data structure regarding the component includes an indication of the updated version of the component, wherein said determining that an update is available is based on a comparison of the indication of the updated version of the component with an indication of an loaded version of the component, wherein the updated version is different from the loaded version

16. The non-transitory computer-readable storage medium of claim 13, wherein the component is a platform-independent component such that the component is usable in a first platform and in a second platform.

17. The non-transitory computer-readable storage medium of claim 13, wherein the component is a plug-in implemented, at least partially, in a platform-independent scripting language.

18. A system, comprising:

at least one processor; and

a memory comprising program instructions, wherein the program instructions are executable by the at least one processor to;

receive a data structure that includes information regarding a component of an application;

determine, from the data structure, that an updated version of the component is available;

store the updated version of the component in a local data store; and

during execution of the application and without the application shutting down, update the component with the stored updated version of the component;

wherein a time to perform said updating the component with the stored version of the component is substantially similar to a time to perform reading a previous version of the component.

19. The system of claim 18, wherein said updating is performed in response to an occurrence of an event.

20. The system of claim 18, wherein the component is a plug-in implemented, at least partially, in a platform-independent scripting language.