Memory model for a layout engine and scripting engine

• US 9,430,452 B2
• Filed: 06/06/2013
• Issued: 08/30/2016
• Est. Priority Date: 06/06/2013
• Status: Active Grant

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Inventors: Rogers, Justin E, Qu, Yong, Man, Curtis Cheng-Cheng
• Primary Examiner(s): Chen, Qing
• Application Number:
  US13/911,514
• Publication Number:
  US 20140365862A1
• Time in Patent Office: 1,181 Days
• Field of Search: 717/114, 717/115
• US Class Current: 1/1
• CPC Class Codes: G06F 40/143 Markup, e.g. Standard Generalized Markup Language [SGML] or Document Type Definition [DTD]
• CPC Class Codes: G06F 8/30 Creation or generation of source code
• CPC Class Codes: G06F 8/31 Programming languages or programming paradigms
• CPC Class Codes: G06F 9/45508 Runtime interpretation or emulation, e g. emulator loops, bytecode interpretation
• CPC Class Codes: G06F 9/45512 Command shells
• CPC Class Codes: G06F 9/541 via adapters, e.g. between incompatible applications
• CPC Class Codes: G06F 9/547 Remote procedure calls [RPC]; Web services
• CPC Class Codes: G06F 9/548 Object oriented; Remote method invocation [RMI] non-remote method invocation G06F9/449

Abstract

Various embodiments provide an interface between a Web browser'"'"'s layout engine and a scripting engine. The interface enables objects from the layout engine to be recognized by a memory manager in the scripting engine and interact in a streamlined, efficient manner. In accordance with one or more embodiments, the interface allows browser layout engine objects to be created as objects that are native to the scripting engine. Alternately or additionally, in some embodiments, the native objects are further configured to proxy functionality between the layout engine and the scripting engine.

Claims

1. A computer-implemented method comprising:

creating at least one layout engine object in a layout engine memory space;

creating a first scripting language object in a scripting engine memory space, wherein the first scripting language object is bound to the at least one layout engine object via a linkage, wherein the linkage utilizes a custom object that is configured to represent relationships between objects in the scripting engine memory space and objects in the layout engine memory space, and wherein the custom object includes one or more pointers and at least some of the one or more pointers are configured to point to other objects in the scripting engine memory space;

assigning a pointer associated with a second scripting language object to a predefined pointer slot associated with the custom object; and

accessing the second scripting language object using the pointer assigned to the predefined pointer slot associated with the custom object.

2. The computer-implemented method of claim 1, wherein accessing the second scripting language object further comprises accessing the second scripting language object from the scripting engine memory space and without crossing into the layout engine memory space.

3. The computer-implemented method of claim 2, wherein accessing the second scripting language object further comprises accessing the second scripting language object using one or more accessor functions.

4. The computer-implemented method of claim 1, wherein assigning the second scripting language object further comprises accessng the second scripting language object as a property object associated with the first scripting language object.

5. The computer-implemented method of claim 4, wherein the first scripting language object comprises a window object.

6. The computer-implemented method of claim 1, wherein accessing the second scripting language object further comprises performing one or more security checks effective to determine that access to the second scripting language object is allowed.

7. The computer-implemented method of claim 6, wherein at least one security check of the one or more security checks comprises comparing type information associated with a calling object with allowed types associated with access to the second scripting language object.

8. One or more computer-readable hardware storage memories storing one or more computer-executable instructions which, responsive to execution by at least one processor, are configured to:

enable one or more Interface Definition Language (IDL) files and one or more Property Description Language (PDL) files to be created that enable one or more bindings between a Web browser'"'"'s layout engine and an associated scripting engine,

wherein the one or more PDL files are configured to describe one or more scripting language objects,

wherein the one or more IDL files are configured to include one or more attributes associated with the one or more bindings between the Web browser'"'"'s layout engine and the associated scripting engine,

wherein at least one attribute of the one or more attributes is configured to annotate a number of predefined pointer slots to reserve and include in a custom object associated with a scripting language object of the one or more scripting language objects,

wherein the custom object includes one or more pointers and at least some of the one or more pointers are configured to point to other objects in a scripting engine memory space associated with the associated scripting engine, and

wherein at least one attribute of the one or more attributes is configured to annotate information associated with determining allowable access to a scripting language object of the one or more scripting language objects.

9. The one or more computer-readable hardware storage memories of claim 8, wherein the at least one attribute of the one or more attributes is further configured to annotate the number of predefined pointer slots to reserve based, at least in part, on a hierarchy associated with the scripting language object of the one or more scripting language objects.

10. The one or more computer-readable hardware storage memories of claim 8, wherein at least one attribute of the one or more attributes is configured to identify a scripting language object of the one or more scripting language objects to associate with a predefined pointer slot contained within the custom object.

11. The one or more computer-readable hardware storage memories of claim 10, wherein the one or more computer-executable instructions are further configured to enable deferred initialization of the scripting language object of the one or more scripting language objects associated with the predefined pointer slot contained within the custom object, and wherein deferred initialization comprises initializing the scripting language object of the one or more scripting language objects when the scripting language object of the one or more scripting language objects is accessed.

12. The one or more computer-readable hardware storage memories of claim 10, wherein the one or more bindings further comprise one or more accessor functions associated with the scripting language object of the one or more scripting language objects associated with the predefined pointer slot contained within the custom object, and wherein the one or more accessor functions are configured to call functionality within the scripting engine memory space associated with the associated scripting engine and without crossing into a layout engine memory space associated with the Web browser'"'"'s layout engine.

13. A system comprising:

at least one processor; and

One or more computer-readable hardware storage memories storing one or more computer-executable instructions which, responsive to execution by the at least one processor, are configured to;

create at least one layout engine object in a layout engine memory space;

create a first scripting language object in a scripting engine memory space, wherein the first scripting language object is bound to the at least one layout engine object via a linkage, wherein the linkage utilizes a custom object that is configured to represent relationships between objects in the scripting engine memory space and objects in the layout engine memory space, and wherein the custom object includes one or more pointers and at least some of the one or more pointers are configured to point to other objects in the scripting engine memory space;

assign a pointer associated with a second scripting language object to a predefined pointer slot associated with the custom object, wherein the second scripting language object comprises a property object associated with the at least one layout engine object; and

access the second scripting language object using the pointer assigned to the predefined pointer slot associated with the custom object using an accessor function associated with the property object while remaining in the scripting engine memory space.

14. The system of claim 13, wherein the accessor function comprises a getter accessor function described within the scripting engine memory space.

15. The system of claim 13, wherein the one or more computer-executable instructions to access the second scripting language object are further configured to access the second scripting language object as a property object associated with a window object.

16. The system of claim 15, wherein the second scripting language object comprises a document object.

17. The system of claim 13, wherein the one or more computer-executable instructions to access the second scripting language object are further configured to perform at least one security check, in the scripting engine memory space, effective to determine that access to the second scripting language object is allowed.

18. The system of claim 17, wherein the one or more computer-executable instructions are further configured to:

determine, in the scripting engine memory space, that access to the second scripting language object is disallowed; and

disallow access to the second scripting language object.

19. The system of claim 13, wherein the one or more computer-executable instructions are further configured to initialize the second scripting language object responsive to the access.