Concurrent parsing and processing of HTML and JAVASCRIPT®

• US 8,413,047 B2
• Filed: 05/12/2011
• Issued: 04/02/2013
• Est. Priority Date: 05/12/2011
• Status: Active Grant

• Current Assignee: Qualcomm, Inc.
• Original Assignee: Qualcomm, Inc.
• Inventors: Vick, Christopher A., Wang, Bin, Reshadi, Mehrdad Mohammad H
• Primary Examiner(s): Hutton, Jr., Doug
• Assistant Examiner(s): DYER, ANDREW R
• Application Number:
  US13/106,064
• Publication Number:
  US 20120290924A1
• Time in Patent Office: 691 Days
• Field of Search: 715/234, 715/237, 717/115, 717/119, 717/139
• US Class Current: 715/237
• CPC Class Codes: G06F 40/143 Markup, e.g. Standard Generalized Markup Language [SGML] or Document Type Definition [DTD]
• CPC Class Codes: G06F 40/221 Parsing markup language streams streaming G06F40/149
• CPC Class Codes: G06F 40/226 Validation

Abstract

The aspects enable a processor to concurrently execute markup language code (e.g., HTML) having embedded scripting language code (e.g., JAVASCRIPT®) during a page load operation by a browser. A markup language parser parses markup language code until embedded scripting language code is encountered. The segment of embedded scripting language code is extracted for execution by a scripting language engine which proceeds concurrently with speculative parsing of the markup language code. Markup language code generated by execution of scripting language code is evaluated to determine if it is well formed, and a partial rollback of the markup language parse and re-parsing of portions of the markup language code is accomplished if not. Concurrent parsing of markup language code and execution of scripting language code, with partial roll back of the parsing process when necessary, continues until all markup language code has been parsed and all scripting language code has been executed.

Claims

1. A method for executing a markup language code in a processor, comprising:

receiving in the processor a request to load a web page;

receiving markup language code associated with the requested web page, the markup language code including embedded scripting language code;

parsing the received markup language code to generate parse data until a segment of scripting language code is encountered;

packaging the encountered segment of scripting language code and parsing state information in an execution state package upon encountering the segment of scripting language code;

storing the execution state package in a scripting language script queue;

continuing parsing the received markup language code;

obtaining the segment of scripting language code from the scripting language script queue;

executing the obtained segment of scripting language code concurrent with continued parsing of the markup language code;

determining whether markup language code generated from the execution of the obtained segment of scripting language code is well formed;

when it is determined that the generated markup language code is well formed, storing the generated markup language code; and

when it is determined that the generated markup language is not well formed;

retrieving the parsing state information packaged in the execution state package;

discarding parse data resulting from parsing of the markup language code after a point in the markup language code identified by the retrieved execution state package; and

re-initiating parsing of the markup language code from the point in the markup language code identified by the retrieved execution state package.

2. The method of claim 1, wherein packaging the encountered segment of scripting language code and state information in an execution state package comprises:

extracting the encountered segment of scripting language code embedded in the markup language code;

storing a memory location address associated with the extracted segment of the scripting language code;

storing an execution context associated with the extracted segment of the scripting language code; and

generating the execution state package to include references to the stored memory location address, stored execution context, and the extracted segment of the scripting language code.

3. The method of claim 1, wherein storing the execution state package in a scripting language script queue comprises storing the execution state package in a rear terminal position of the scripting language script queue.

4. The method of claim 1, wherein obtaining the segment of scripting language from the scripting language script queue is initiated in response to an execution state package being stored in the scripting language script queue.

5. The method of claim 1, wherein obtaining the segment of scripting language from the scripting language script queue comprises extracting the segment of scripting language code from the execution state package stored in a front terminal of the scripting language script queue.

6. The method of claim 1, wherein executing the obtained segment of scripting language is performed independent of the concurrently executing parsing process and comprises:

monitoring the scripting language script queue to determine if the scripting language script queue contains scripts available for processing;

retrieving the execution state package from a front terminal of the scripting language script queue when it is determined that the scripting language script queue contains scripts for processing;

extracting scripting language code from the retrieved execution state package;

evaluating extracted scripting language code to identify specific characteristics that allow the scripting language execution process to insert a second unit of markup language code into the received markup language code associated with the requested web page; and

executing the extracted scripting language code using identified specific characteristics to generate the second unit of markup language code.

7. The method of claim 1, further comprising:

repeating operations of;

parsing the received markup language code,

packaging encountered scripting language code into execution packages,

storing the execution packages in the scripting language script queue,

continuing parsing the received markup language code,

obtaining the segment of scripting language code from the scripting language script queue, and

executing the obtained segment of scripting language code concurrent with continued parsing of the markup language code,

until all markup language code has been parsed and all scripting language code has been executed.

8. The method of claim 1, wherein storing the generated markup language comprises:

inserting the generated markup language code into the received markup language code associated with the requested web page.

9. The method of claim 1, further comprising:

determining whether parsing of the markup language code has completed;

determining whether execution of all scripting language code has completed; and

rendering the requested web page upon determining that both parsing of the markup language code has completed and execution of all scripting language code has completed.

10. The method of claim 1, wherein the markup language is HTML.

11. The method of claim 1, wherein determining whether markup language code generated from execution of the obtained segment of scripting language is well formed comprises parsing the generated markup language code with a well formed parser to determine whether the generated markup language code is well formed.

12. The method of claim 11, further comprising:

notifying a markup language parser when it is determined that the generated markup language code is not well formed.

13. A computing device for executing a markup language, comprising:

a memory; and

a processor coupled to the memory, wherein the processor is configured with processor-executable instructions to perform operations comprising;

receiving in the processor a request to load a web page;

receiving markup language code associated with the requested web page, the markup language code including embedded scripting language code;

parsing the received markup language code to generate parse data until a segment of scripting language code is encountered;

packaging the encountered segment of scripting language code and parsing state information in an execution state package upon encountering the segment of scripting language code;

storing the execution state package in a scripting language script queue;

continuing parsing the received markup language code;

obtaining the segment of scripting language code from the scripting language script queue;

executing the obtained segment of scripting language code concurrent with continued parsing of the markup language code;

determining whether markup language code generated from the execution of the obtained segment of scripting language code is well formed;

when it is determined that the generated markup language code is well formed, storing the generated markup language code; and

when it is determined that the generated markup language is not well formed;

retrieving the parsing state information packaged in the execution state package;

discarding parse data resulting from parsing of the markup language code after a point in the markup language code identified by the retrieved execution state package; and

re-initiating parsing of the markup language code from the point in the markup language code identified by the retrieved execution state package.

14. The computing device of claim 13, wherein the processor is further configured with processor-executable instructions such that packaging the encountered segment of scripting language code and state information in an execution state package comprises:

extracting the encountered segment of scripting language code embedded in the markup language code;

storing a memory location address associated with the extracted segment of the scripting language code;

storing an execution context associated with the extracted segment of the scripting language code; and

generating the execution state package to include references to the stored memory location address, stored execution context, and the extracted segment of the scripting language code.

15. The computing device of claim 13, wherein the processor is further configured with processor-executable instructions such that storing the execution state package in a scripting language script queue comprises storing the execution state package in a rear terminal position of the scripting language script queue.

16. The computing device of claim 13, wherein the processor is further configured with processor-executable instructions such that obtaining the segment of scripting language from the scripting language script queue is initiated in response to an execution state package being store in the scripting language script queue.

17. The computing device of claim 13, wherein the processor is further configured with processor-executable instructions such that obtaining the segment of scripting language from the scripting language script queue comprises extracting the segment of scripting language code from the execution state package stored in a front terminal of the scripting language script queue.

18. The computing device of claim 13, wherein the processor is further configured with processor-executable instructions such that executing the obtained segment of scripting language is performed independent of the concurrently executing parsing process and comprises:

monitoring the scripting language script queue to determine if the scripting language script queue contains scripts available for processing;

retrieving the execution state package from a front terminal of the scripting language script queue when it is determined that the scripting language script queue contains scripts for processing;

extracting scripting language code from the retrieved execution state package;

evaluating extracted scripting language code to identify specific characteristics that allow the scripting language execution process to insert a second unit of markup language code into the received markup language code associated with the requested web page; and

executing the extracted scripting language code using identified specific characteristics to generate the second unit of markup language code.

19. The computing device of claim 13, wherein the processor is configured with processor-executable instructions to perform operations further comprising:

repeating operations of;

parsing the received markup language code,

packaging encountered scripting language code into execution packages,

storing the execution packages in the scripting language script queue,

continuing parsing the received markup language code,

obtaining the segment of scripting language code from the scripting language script queue, and

executing the obtained segment of scripting language code concurrent with continued parsing of the markup language code,

until all markup language code has been parsed and all scripting language code has been executed.

20. The computing device of claim 13, wherein the processor is further configured with processor-executable instructions such that storing the generated markup language comprises:

inserting the generated markup language code into the received markup language code associated with the requested web page.

21. The method of claim 13, wherein the processor is configured with processor-executable instructions to perform operations further comprising:

determining whether parsing of the markup language code has completed;

determining whether execution of all scripting language code has completed; and

rendering the requested web page upon determining that both parsing of the markup language code has completed and execution of all scripting language code has completed.

22. The computing device of claim 13, wherein the processor is further configured with processor-executable instructions such that the markup language is processed as HTML.

23. The method of claim 13, wherein the processor is further configured with processor-executable instructions such that determining whether markup language code generated from execution of the obtained segment of scripting language is well formed comprises parsing the generated markup language code with a well formed parser to determine whether the generated markup language code is well formed.

24. The computing device of claim 23, wherein the processor is configured with processor-executable instructions to perform operations further comprising:

notifying a markup language parser when it is determined that the generated markup language code is not well formed.

25. A non-transitory storage medium having stored thereon processor-executable software instructions configured to cause a processor to perform operations for executing a markup language code, the operations comprising:

receiving in the processor a request to load a web page;

receiving markup language code associated with the requested web page, the markup language code including embedded scripting language code;

parsing the received markup language code to generate parse data until a segment of scripting language code is encountered;

packaging the encountered segment of scripting language code and parsing state information in an execution state package upon encountering the segment of scripting language code;

storing the execution state package in a scripting language script queue;

continuing parsing the received markup language code;

obtaining the segment of scripting language code from the scripting language script queue;

executing the obtained segment of scripting language code concurrent with continued parsing of the markup language code;

determining whether markup language code generated from the execution of the obtained segment of scripting language code is well formed;

when it is determined that the generated markup language code is well formed, storing the generated markup language code; and

when it is determined that the generated markup language is not well formed;

retrieving the parsing state information packaged in the execution state package;

discarding parse data resulting from parsing of the markup language code after a point in the markup language code identified by the retrieved execution state package; and

re-initiating parsing of the markup language code from the point in the markup language code identified by the retrieved execution state package.

26. The non-transitory storage medium of claim 25, wherein the stored processor-executable software instructions are configured to cause a processor to perform operations such that packaging the encountered segment of scripting language code and state information in an execution state package comprises:

extracting the segment of scripting language code embedded in the markup language code;

storing a memory location associated with the extracted portion of the scripting language code;

storing an execution context associated with the extracted portion of the scripting language code; and

generating the execution state package to include references to the stored memory location address, stored execution context, and the extracted segment of the scripting language code.

27. The non-transitory storage medium of claim 25, wherein the stored processor-executable software instructions are configured to cause a processor to perform operations such that storing the execution state package in a scripting language script queue comprises storing the execution state package in a rear terminal position of the scripting language script queue.

28. The non-transitory storage medium of claim 25, wherein the stored processor-executable software instructions are configured to cause a processor to perform operations such that obtaining the segment of scripting language from the scripting language script queue is initiated in response to an execution state package being store in the scripting language script queue.

29. The non-transitory storage medium of claim 25, wherein the stored processor-executable software instructions are configured to cause a processor to perform operations such that obtaining the segment of scripting language from the scripting language script queue comprises extracting the segment of scripting language code from the execution state package stored in a front terminal of the scripting language script queue.

30. The non-transitory storage medium of claim 25, wherein the stored processor-executable software instructions are configured to cause a processor to perform operations such that executing the obtained segment of scripting language is performed independent of the concurrently executing parsing process and comprises:

monitoring the scripting language script queue to determine if the scripting language script queue contains scripts available for processing;

retrieving the execution state package from a front terminal of the scripting language script queue when it is determined that the scripting language script queue contains scripts for processing;

extracting scripting language code from the retrieved execution state package;

evaluating extracted scripting language code to identify specific characteristics that allow the scripting language execution process to insert a second unit of markup language code into the received markup language code associated with the requested web page; and

executing the extracted scripting language code using identified specific characteristics to generate the second unit of markup language code.

31. The non-transitory storage medium of claim 25, wherein the stored processor-executable software instructions are configured to cause a processor to perform operations further comprising:

repeating operations of;

parsing the received markup language code,

packaging encountered scripting language code into execution packages,

storing the execution packages in the scripting language script queue,

continuing parsing the received markup language code,

obtaining the segment of scripting language code from the scripting language script queue, and

executing the obtained segment of scripting language code concurrent with continued parsing of the markup language code continue,

until all markup language code has been parsed and all scripting language code has been executed.

32. The non-transitory storage medium of claim 25, wherein the stored processor-executable software instructions are configured to cause a processor to perform operations such that storing the generated markup language comprises:

inserting the generated markup language code into the received markup language code associated with the requested web page.

33. The non-transitory storage medium of claim 25, wherein the stored processor-executable software instructions are configured to cause a processor to perform operations further comprising:

determining whether parsing of the markup language code has completed;

determining whether execution of all scripting language code has completed; and

rendering the requested web page upon determining that both parsing of the markup language code has completed and execution of all scripting language code has completed.

34. The non-transitory storage medium of claim 25, wherein the stored processor-executable software instructions are configured to cause a processor to perform operations such that the markup language is processed as HTML.

35. The non-transitory storage medium of claim 25, wherein the stored processor-executable software instructions are configured to cause a processor to perform operations such that determining whether markup language code generated from execution of the obtained segment of scripting language is well formed comprises parsing the generated markup language code with a well formed parser to determine whether the generated markup language code is well formed.

36. The non-transitory storage medium of claim 35, wherein the stored processor-executable software instructions are configured to cause a processor to perform operations further comprising:

notifying a markup language parser when it is determined that the generated markup language code is not well formed.