Memory Model for a Layout Engine and Scripting Engine

Patent metadata

Field	Value
Publication number	US-2016335233-A1
Application number	US-201615220033-A
Country	US
Kind code	A1
Filing date	Jul 26, 2016
Priority date	Jun 6, 2013
Publication date	Nov 17, 2016
Grant date	—

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.

First claim

1 . A computing device comprising:
at least one processor; memory coupled to the at least one processor; a web browser that includes a layout engine and a scripting engine; a first memory space within the memory that forms a first domain in which the computing device is configured to execute the layout engine; a second memory space within the memory that forms a second domain that is separate from the first domain and in which the computing device is configured to execute the scripting engine; and the layout engine and the scripting engine configured for securely communicating with each other across the first domain and the second domain via a first object and a second object, the first object in the first memory space and native to the layout engine, the first object bound to a corresponding second object in the second memory space and native to the scripting engine.

2 . The computing device of claim 1 where the securely communicating comprises the layout engine and the scripting engine calling functionality within each other across the first domain and the second domain.

3 . The computing device of claim 1 where the securely communicating comprises redirecting a call, based on a direct call by the scripting engine to the second object in the second memory space and native to the scripting engine, from the second object in the second memory space and native to the scripting engine into the first object in the first memory space and native to the layout engine.

4 . The computing device of claim 1 where the securely communicating is via a bridge function interposed between the layout engine and the scripting engine.

5 . The computing device of claim 4 where the second object in the second memory space and native to the scripting engine and the first object in the first memory space and native to the layout engine are bound together via an access link provided via the bridge function.

6 . The computing device of claim 4 where the bridge function is configured to validate calling objects including the first object and the second object, where a validated calling object has a correct calling type.

7 . The computing device of claim 4 where the bridge function is configured to be wrapped by a native function of the scripting engine.

8 . A method performed on a computing device comprising at least one processor and memory, the method comprising:
first executing, by the computing device, a layout engine in a first domain formed in a first memory space within the memory; second executing, by the computing device, a scripting engine in a second domain formed second memory space within the memory; and securely communicating, by the layout engine and the scripting engine with each other, across the first domain and the second domain via a first object and a second object, the first object in the first memory space and native to the layout engine, the first object bound to a corresponding second object in the second memory space and native to the scripting engine.

9 . The method of claim 8 where the securely communicating comprises the layout engine and the scripting engine calling functionality within each other across the first domain and the second domain.

10 . The method of claim 8 where the securely communicating comprises redirecting a call, based on a direct call by the scripting engine to the second object in the second memory space and native to the scripting engine, from the second object in the second memory space and native to the scripting engine into the first object in the first memory space and native to the layout engine.

11 . The method of claim 8 where the securely communicating is via a bridge function interposed between the layout engine and the scripting engine.

12 . The method of claim 11 where the second object in the second memory space and native to the scripting engine and the first object in the first memory space and native to the layout engine are bound together via an access link provided via the bridge function.

13 . The method of claim 11 where the bridge function is configured to validate calling objects including the first object and the second object, where a validated calling object has a correct calling type.

14 . The method of claim 11 where the bridge function is configured to be wrapped by a native function of the scripting engine.

15 . At least one hardware computer-readable medium that includes computer-executable instructions that, based on execution by at least one processor of a computing device that further comprises memory, configure the computing device to perform actions comprising:
first executing, by the computing device, a layout engine in a first domain formed in a first memory space within the memory; second executing, by the computing device, a scripting engine in a second domain formed second memory space within the memory; and securely communicating, by the layout engine and the scripting engine with each other, across the first domain and the second domain via a first object and a second object, the first object in the first memory space and native to the layout engine, the first object bound to a corresponding second object in the second memory space and native to the scripting engine.

16 . The method of claim 15 where the securely communicating comprises the layout engine and the scripting engine calling functionality within each other across the first domain and the second domain.

17 . The method of claim 15 where the securely communicating comprises redirecting a call, based on a direct call by the scripting engine to the second object in the second memory space and native to the scripting engine, from the second object in the second memory space and native to the scripting engine into the first object in the first memory space and native to the layout engine.

18 . The method of claim 15 where the securely communicating is via a bridge function interposed between the layout engine and the scripting engine.

19 . The method of claim 18 where the second object in the second memory space and native to the scripting engine and the first object in the first memory space and native to the layout engine are bound together via an access link provided via the bridge function.

20 . The method of claim 18 where the bridge function is configured to validate calling objects including the first object and the second object, where a validated calling object has a correct calling type, or where the bridge function is configured to be wrapped by a native function of the scripting engine.

Assignees

• Microsoft Technology Licensing Llc

Inventors

• Qu Yong
• Man Curtis Cheng-Cheng
• Rogers Justin E

Classifications

• G06F8/30

  Creation or generation of source code · CPC title

• G06F8/31

  Programming languages or programming paradigms · CPC title

• G06F9/547

  Remote procedure calls [RPC]; Web services · CPC title

• G06F9/45508

  Runtime interpretation or emulation, e g. emulator loops, bytecode interpretation · CPC title

• G06F9/45512

  Command shells · CPC title