SYSTEMS AND METHODS FOR MANAGING LOADING PRIORITY OR SEQUENCING OF FRAGMENTS OF A WEB OBJECT

• US 20150088969A1
• Filed: 01/24/2014
• Published: 03/26/2015
• Est. Priority Date: 09/20/2013
• Status: Active Grant

• Current Assignee: Yottaa, Inc.
• Original Assignee: Yottaa, Inc.
• Inventors: Wei, Coach K., Buffone, Robert
• Granted Patent: US 9,282,145 B2
• Time in Patent Office: Days
• US Class Current: 709/203
• CPC Class Codes: G06F 16/00 Information retrieval; Database structures therefor; File system structures therefor
• CPC Class Codes: G06F 2209/541 Client-server
• CPC Class Codes: G06F 2209/542 Intercept
• CPC Class Codes: G06F 40/143 Markup, e.g. Standard Generalized Markup Language [SGML] or Document Type Definition [DTD]
• CPC Class Codes: G06F 9/46 Multiprogramming arrangements
• CPC Class Codes: G06F 9/54 Interprogram communication
• CPC Class Codes: H04L 67/01 Protocols
• 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/34 involving the movement of software or configuration parameters network booting or remote initial program loading [RIPL] G06F9/4416
• CPC Class Codes: H04L 67/561 Adding application-functional data or data for application control, e.g. adding metadata
• CPC Class Codes: H04L 67/564 Enhancement of application control based on intercepted application data
• CPC Class Codes: H04L 67/565 Conversion or adaptation of application format or content adding application control or application functional data H04L67/561

Abstract

This disclosure is directed to methods and systems for managing rendering of a web page in a browser. A client operated by a user may execute code within a first fragment of a web page as the first fragment is presented to the user. The code may be injected into the first fragment by an intermediary between the client and a server of the web page. The intermediary may have split the web page into the first fragment and a plurality of fragments, and may have modified a default rendering characteristic for each of the plurality of fragments. Each of the modified rendering characteristic may include a trigger and action for rendering of a corresponding fragment. The executing code may dynamically detect a trigger for rendering of a second fragment from the plurality of fragments. The executing code may initiate a corresponding action for rendering of the second fragment.

Claims

1. A method for managing rendering of a web page in a browser, comprising:

(a) executing, by a client operated by a user, code within a first fragment of a web page as the first fragment is presented to the user, the code injected into the first fragment by an intermediary between the client and a server of the web page, the intermediary having split the web page into the first fragment and a plurality of fragments, and modified a default rendering characteristic derived from the server for each of the plurality of fragments, wherein the default rendering characteristic comprises rendering the corresponding fragment in sequence with respect to other fragments as arranged in the web page, and each modified rendering characteristic comprises a trigger and an action for rendering of a corresponding fragment independent of other fragments of the plurality of fragments;

(b) dynamically detecting, by the executing code based on a corresponding modified rendering characteristic, a trigger for rendering of a second fragment from the plurality of fragments, the trigger comprising one of;

a user event and a document object model event at the client, that involves a display or use of the second fragment; and

(c) initiating, by the executing code responsive to the detected trigger, a corresponding action for rendering of the second fragment within the first fragment.

2. The method of claim 1, comprising sending, by the client, a request to the server for the web page, the request intercepted by the intermediary.

3. The method of claim 1, comprising receiving, by the client from the intermediary, the first fragment with the injected code.

4. The method of claim 1, wherein (a) comprises executing the code, the code comprising at least one of:

code expressed in ECMAScript language or a language similar or related to the ECMAScript language, code expressed in ActionScript language, code expressed in hypertext markup language, code expressed in visual basic language, a plug-in, code referencing a browser plug-in, and code referencing a native module.

5. The method of claim 1, comprising receiving at least one of the plurality of fragments from the intermediary, each of the plurality of fragments having a rendering characteristic modified by the intermediary based on a configuration.

6. The method of claim 1, further comprising performing a pre-trigger action for the second fragment prior to detecting the trigger, the pre-trigger action comprising at least one of:

withholding rendering of the second fragment, displaying nothing at an identified location of the web page, and displaying at least one item, the at least one item comprising at least one of;

an indicator or message indicating that an item is loading, a temporary or placeholder item or image, an advertisement, and a special call-to-action item.

7. The method of claim 1, wherein (b) comprises detecting a user event comprising one of:

a click event, a tap event, a touch event, a mouse-over event and a scroll event on the web page.

8. The method of claim 1, wherein (b) comprises detecting that a viewing region of the client corresponds to a portion of the web page involving a display or use of the second fragment of the web page.

9. The method of claim 1, wherein (b) comprises detecting that a viewing region of the client corresponds to a portion of the first fragment that includes a unique identifier for the second fragment.

10. The method of claim 1, wherein (c) comprises initiating the corresponding action, the corresponding action comprising replacing one or more displayed items with the rendering of the second fragment.

11. The method of claim 1, wherein (c) comprises initiating the corresponding action, the corresponding action comprising rendering the second fragment immediately or as soon as the second fragment is available for rendering.

12. The method of claim 1, wherein (c) comprises initiating the corresponding action, the corresponding action comprising rendering the second fragment based on a specified delay or after a subset of the plurality of fragments have been loaded.

13. The method of claim 1, wherein (c) comprises initiating the corresponding action, the corresponding action comprising sending a request to the server for downloading a resource, the second fragment or a related fragment.

14. The method of claim 1, wherein (c) comprises initiating the corresponding action, the corresponding action comprising sending a request to the server, the request intercepted or received by the intermediary.

15. The method of claim 1, wherein (c) comprises initiating the corresponding action for rendering the second fragment, the second fragment comprising one of at least a portion of:

an image, a cascading style sheet (CSS), a script, a video object, an audio object, a flash file or small web format (SWF) file, and a HTML file.

16. A system for managing rendering of a web page in a browser, the system comprising:

a processor of a client operated by a user;

a browser executing on the processor; and

code injected into a first fragment of a web page by an intermediary between the client and a server of the web page, the code executed by the browser as the first fragment is presented to the user, the intermediary having split the web page into the first fragment and a plurality of fragments and modified a default rendering characteristic derived from the server for each of the plurality of fragments, wherein the default rendering characteristic comprises rendering the corresponding fragment in sequence with respect to other fragments as arranged in the web page, and each modified rendering characteristic comprises a trigger and an action for rendering of a corresponding fragment independent of other fragments of the plurality of fragments, the executing code;

dynamically detecting, based on a corresponding modified rendering characteristic, a trigger for rendering of a second fragment from the plurality of fragments, the trigger comprising one of;

a user event and a document object model event at the client, that involves a display or use of the second fragment, and

initiating, responsive to the detected trigger, a corresponding action for rendering of the second fragment within the first fragment.

17. The system of claim 16, wherein the browser sends a request to the server for the web page, the request intercepted by the intermediary.

18. The system of claim 16, wherein the browser receives from the intermediary the first fragment with the injected code.

19. The system of claim 16, wherein the code comprises at least one of:

code expressed in ECMAScript language or a language similar or related to the ECMAScript language, code expressed in ActionScript language, code expressed in hypertext markup language, code expressed in visual basic language, a plug-in, code referencing a browser plug-in, and code referencing a native module.

20. The system of claim 16, wherein the browser receives at least one of the plurality of fragments from the intermediary, each of the plurality of fragments having a rendering characteristic modified by the intermediary based on a configuration.

21. The system of claim 16, wherein the browser performing a pre-trigger action for the corresponding fragment prior to detecting the trigger, the pre-trigger action comprising at least one of:

withholding rendering of the second fragment, displaying nothing at an identified location of the web page, and displaying at least one item, the at least one item comprising at least one of;

an indicator or message indicating that an item is loading, a temporary or placeholder item or image, an advertisement, and a special call-to-action item.

22. The system of claim 16, wherein the executing code detects a user event comprising one of:

a click event, a tap event, a touch event, a mouse-over event and a scroll event on the web page.

23. The system of claim 16, wherein the executing code detects that a viewing region of the client corresponds to a portion of the web page involving a display or use of the second fragment of the web page.

24. The system of claim 16, wherein the executing code detects that a viewing region of the client corresponds to a portion of the first fragment that includes a unique identifier for the second fragment.

25. The system of claim 16, wherein the executing code initiates the corresponding action, the corresponding action comprising replacing one or more displayed items with the rendering of the second fragment.

26. The system of claim 16, wherein the executing code initiates the corresponding action, the corresponding action comprising rendering the second fragment immediately or as soon as the second fragment is available for rendering.

27. The system of claim 16, wherein (c) wherein the executing code initiates the corresponding action, the corresponding action comprising rendering the second fragment based on a specified delay or after a subset of the plurality of fragments have been loaded.

28. The system of claim 16, wherein the executing code initiates the corresponding action, the corresponding action comprising sending a request to the server for downloading a resource, the second fragment or a related fragment.

29. The system of claim 16, wherein the executing code initiates the corresponding action, the corresponding action comprising sending a request to the server, the request intercepted or received by the intermediary.

30. The system of claim 16, wherein the executing code initiates the corresponding action for rendering the second fragment, the second fragment comprising one of at least a portion of:

an image, a cascading style sheet (CSS), a script, a video object, an audio object, a flash file or small web format (SWF) file, and a HTML file.