PROVIDING AN IMPROVED WEB USER INTERFACE FRAMEWORK FOR BUILDING WEB APPLICATIONS

• US 20170153883A1
• Filed: 11/14/2016
• Published: 06/01/2017
• Est. Priority Date: 08/06/2013
• Status: Active Grant

• Current Assignee: Salesforce.com, Inc.
• Original Assignee: Salesforce.com, Inc.
• Inventors: Oliver, Gordon, Abbott, III, Freeland Knight
• Granted Patent: US 10,331,432 B2
• Time in Patent Office: Days
• CPC Class Codes: G06F 8/65 Updates security arrangements therefor G06F21/57
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 67/10 in which an application is distributed across nodes in the network software deployment G06F8/60; multiprogramming arrangements G06F9/46
• CPC Class Codes: H04L 67/306 User profiles

Abstract

Disclosed are methods, systems, and computer program products for updating a web application displayed on a client machine. In some implementations, a server maintains a database of application identifiers identifying instances of one or more web applications. The server receives, from a first client machine, a communication identifying a first web application and a first application identifier, the instance of the first web application being associated with one or more components. The server determines that the first application identifier is not included in the database of application identifiers, and generates an updated application identifier for the instance of the first web application based on component version identifiers of the one or more components. The server stores the updated application identifier and transmits a notification to the first client machine indicating that the instance of the first web application is out-of-date.

Claims

1. (canceled)

2. A system comprising:

a database system implemented using a server system comprising one or more processors, the database system configurable to cause;

maintaining, at a database of the database system, at least one web application comprising a plurality of components;

identifying a first component version identifier of a first one of the components;

identifying a second component version identifier of a second one of the components;

generating or updating, using a dependency tree associated with the components, a first application identifier based at least on the first component version identifier and the second component version identifier;

determining that the first component has been updated, the updated first component having an updated first component version identifier;

processing a request to access the web application;

identifying the updated first component version identifier;

generating or updating, using the dependency tree associated with the components, a second application identifier based at least on the updated first component version identifier and the second component version identifier;

determining that the first application identifier is different from the second application identifier; and

providing a notification indicating that the a new version of the web application is available.

3. The system of claim 2, wherein the determination that the first application identifier is different from the second application identifier identifies at least one out-of-date component associated with the web application.

4. The system of claim 2, wherein generating or updating the first application identifier comprises:

traversing the dependency tree to compute a hash according to at least a first location of the dependency tree associated with the first component version identifier and a second location of the dependency tree associated with the second component version identifier, the first location being higher in the dependency tree than the second location.

5. The system of claim 2, the database system further configurable to cause:

storing the first application identifier in the database of the database system;

storing the second application identifier in the database of the database system;

determining that the second component has been updated, the updated second component having an updated second component version identifier;

generating or updating, using the dependency tree associated with the components, a third application identifier based at least on the updated first component version identifier and the updated second component version identifier; and

storing the third application identifier in the database of the database system.

6. The system of claim 2, wherein the first component is identified from the components according to one or more of:

a role of a user, a position of the user, or a personalization setting of the user.

7. The system of claim 2, wherein the request to access the web application is an XHR (XMLHttpRequest) request configured to trigger an action at the database system.

8. The system of claim 2, wherein the second application identifier is stored in a cache of a client device.

9. A method comprising:

maintaining, at a database of a database system, at least one web application comprising a plurality of components;

identifying a first component version identifier of a first one of the components;

identifying a second component version identifier of a second one of the components;

generating or updating, using a dependency tree associated with the components, a first application identifier based at least on the first component version identifier and the second component version identifier;

determining that the first component has been updated, the updated first component having an updated first component version identifier;

processing a request to access the web application;

identifying the updated first component version identifier;

generating or updating, using the dependency tree associated with the components, a second application identifier based at least on the updated first component version identifier and the second component version identifier;

determining that the first application identifier is different from the second application identifier; and

providing a notification indicating that the a new version of the web application is available.

10. The method of claim 9, wherein the determination that the first application identifier is different from the second application identifier identifies at least one out-of-date component associated with the web application.

11. The method of claim 9, wherein generating or updating the first application identifier comprises:

traversing the dependency tree to compute a hash according to at least a first location of the dependency tree associated with the first component version identifier and a second location of the dependency tree associated with the second component version identifier, the first location being higher in the dependency tree than the second location.

12. The method of claim 9, the method further comprising:

storing the first application identifier in the database of the database system;

storing the second application identifier in the database of the database system;

determining that the second component has been updated, the updated second component having an updated second component version identifier;

generating or updating, using the dependency tree associated with the components, a third application identifier based at least on the updated first component version identifier and the updated second component version identifier; and

storing the third application identifier in the database of the database system.

13. The method of claim 9, wherein the first component is identified from the components according to one or more of:

a role of a user, a position of the user, or a personalization setting of the user.

14. The method of claim 9, wherein the request to access the web application is an XHR (XMLHttpRequest) request configured to trigger an action at the database system.

15. The method of claim 9, wherein the second application identifier is stored in a cache of a client device.

16. A computer program product comprising computer-readable program code to be executed by one or more processors when retrieved from a non-transitory computer-readable medium, the program code including instructions configurable to cause:

maintaining, at a database of a database system, at least one web application comprising a plurality of components;

identifying a first component version identifier of a first one of the components;

identifying a second component version identifier of a second one of the components;

generating or updating, using a dependency tree associated with the components, a first application identifier based at least on the first component version identifier and the second component version identifier;

determining that the first component has been updated, the updated first component having an updated first component version identifier;

processing a request to access the web application;

identifying the updated first component version identifier;

generating or updating, using the dependency tree associated with the components, a second application identifier based at least on the updated first component version identifier and the second component version identifier;

determining that the first application identifier is different from the second application identifier; and

providing a notification indicating that the a new version of the web application is available.

17. The computer program product of claim 16, wherein the determination that the first application identifier is different from the second application identifier identifies at least one out-of-date component associated with the web application.

18. The computer program product of claim 16, wherein generating or updating the first application identifier comprises:

traversing the dependency tree to compute a hash according to at least a first location of the dependency tree associated with the first component version identifier and a second location of the dependency tree associated with the second component version identifier, the first location being higher in the dependency tree than the second location.

19. The computer program product of claim 16, the instructions further configurable to cause:

storing the first application identifier in the database of the database system;

storing the second application identifier in the database of the database system;

determining that the second component has been updated, the updated second component having an updated second component version identifier;

generating or updating, using the dependency tree associated with the components, a third application identifier based at least on the updated first component version identifier and the updated second component version identifier; and

storing the third application identifier in the database of the database system.

20. The computer program product of claim 16, wherein the first component is identified from the components according to one or more of:

a role of a user, a position of the user, or a personalization setting of the user.

21. The computer program product of claim 16 wherein the second application identifier is stored in a cache of a client device.