Event-driven module loading

• US 8,346,889 B1
• Filed: 09/30/2011
• Issued: 01/01/2013
• Est. Priority Date: 03/24/2010
• Status: Active Grant

• Current Assignee: Google LLC (Alphabet Inc.)
• Original Assignee: Google Inc. (Alphabet Inc.)
• Inventors: Chiu, Bikin, Kennberg, Alex, Thomas, Neil Richard
• Primary Examiner(s): JEAN, FRANTZ B
• Application Number:
  US13/249,419
• Time in Patent Office: 459 Days
• Field of Search: 709/201, 709/203, 709/218, 709/219, 709/217, 717/100, 717/106, 717/136, 717/140
• US Class Current: 709/217
• CPC Class Codes: G06F 9/44521 Dynamic linking or loading; Link editing at or after load time, e.g. Java class loading

Abstract

Methods, systems, and apparatus, including computer programs encoded on a computer storage medium, for event-driven module loading. In one aspect, a method includes obtaining a mapping for a resource, wherein the mapping identifies one or more events that, upon occurrence, will trigger a dynamic loading of one or more code modules that are referenced by the resource, determining that an event has occurred, identifying one or more of the code modules that are associated with the event, based on the mapping, and dynamically loading the identified code modules.

Claims

1. A system comprising:

one or more computers; and

a computer-readable medium coupled to the one or more computers having instructions stored thereon which, when executed by the one or more computers, cause the one or more computers to perform operations comprising;

accessing historical usage data pertaining to one or more past interactions between a user and a resource;

determining, using the historical usage data, that, on average, the user accesses a first feature of the resource that is associated with a first code module more frequently than the user accesses a second feature of the resource that is associated with a second code module, then adjusting a mapping for the resource to associate an initial load event with the first code module, and to associate an event other than an initial load event with the second code module, wherein the mapping identifies one or more events that, upon occurrence, will trigger a dynamic loading of one or more code modules that are referenced by the resource;

determining that a particular event has occurred;

identifying one or more of the code modules that are associated with the particular event, based on the adjusted mapping; and

dynamically loading the identified code modules.

2. The system of claim 1, wherein the operations further comprise:

loading, before determining that the particular event has occurred, the resource without loading the second code module.

3. The system of claim 1, wherein the first code module further comprises a JavaScript code module.

4. The system of claim 1, wherein:

the initial load event occurs when the resource is initially loaded.

5. The system of claim 1, wherein:

the event other than the initial load event comprises a data communication event that occurs when data of a particular type is communicated.

6. The system of claim 1, wherein:

the event other than the initial load event comprises a Document Object Model (DOM) event that occurs when a DOM event is detected.

7. The system of claim 1, wherein:

the event other than the initial load event comprises a control selection event that occurs when a control is selected on a client device.

8. The system of claim 1, wherein

the event other than the initial load event comprises a view change event that occurs when a user interface of a client device switches from a first view to a second view.

9. The system of claim 1, wherein:

the event other than the initial load event comprises a timer firing event that occurs when a predetermined amount of time elapses.

10. The system of claim 1, wherein the operations further comprise:

determining an identity of the user,

wherein adjusting a mapping for the resource further comprises selecting the mapping, from among a collection of mappings, based on the identity of the user.

11. The system of claim 10, wherein different users are associated with different mappings in the collection.

12. The system of claim 1, wherein the operations further comprise:

invoking the identified code modules; and

responsive to invoking the identified code modules, rendering an updated user interface.

13. A computer-implemented method comprising:

accessing, by a client device, historical usage data pertaining to one or more past interactions between a user and a resource;

determining, using the historical usage data, that, on average, the user accesses a first feature of the resource that is associated with a first code module more frequently than the user accesses a second feature of the resource that is associated with a second code module, then adjusting, by the client device, a mapping to associate a respective timer firing event with each of the first code module and the second code module, wherein the mapping identifies one or more events that, upon occurrence, will trigger a dynamic loading of one or more code modules that are referenced by a resource, and wherein the timing firing event associated with the first code module has a shorter firing time than the timing firing event associated with the second code module;

using the mapping to identify, when a particular event occurs, one or more of the code modules that are associated with the particular event; and

dynamically loading the identified code modules.

14. A computer storage medium encoded with a computer program, the program comprising instructions that when executed by data processing apparatus cause the data processing apparatus to perform operations comprising:

generating information that associates one or more events with one or more code modules that are referenced by a resource;

accessing historical usage data pertaining to one or more past interactions between a user and the resource;

adjusting the information to demote a code module from being associated with an initial load event, to being associated with a data communication event, a control selection event, or a timing firing event;

determining that the data communication event, the control selection event, or the timing firing event has occurred; and

dynamically loading the code module that the adjusted information indicates is associated with the event.