Flexible, event-driven JavaScript server architecture

• US 8,954,989 B1
• Filed: 11/18/2008
• Issued: 02/10/2015
• Est. Priority Date: 11/19/2007
• Status: Active Grant

• Current Assignee: Appcelerator Incorporated (Axway Software SA)
• Original Assignee: Appcelerator Incorporated (Axway Software SA)
• Inventors: Colton, Paul, Sarid, Uri, Lindsey, Kevin Edward
• Primary Examiner(s): Puente, Emerson
• Assistant Examiner(s): MILLS, PAUL V
• Application Number:
  US12/273,539
• Time in Patent Office: 2,275 Days
• Field of Search: None
• US Class Current: 719/313
• CPC Class Codes: G06F 9/54 Interprogram communication
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]

Abstract

A script server architecture is disclosed herein. The script server architecture includes a core comprising means for creating a DOM node in a HTML document, a framework written in JavaScript, the framework comprising a plurality of registered event handlers for performing the business logic of the script server architecture and means for modifying the DOM of a HTML document, and means for bridging the core and the framework.

Claims

1. A server system having a processor and a memory, and comprising:

a core browser engine written in a native language for parsing an HTML document that includes at least one of a server script for execution by a server and a proxy script including a proxied function, for interpreting at least one of the server script and the proxy script, and for creating a Document Object Model (“

DOM”

) corresponding to the HTML document, wherein the core browser engine is executed on a server computer coupled to a client computer over a network;

a server framework component written in an extensible interpreted language different from the language of the core browser engine, the framework component comprising a plurality of registered event handlers for performing the business logic of the server system and for modifying the DOM corresponding to the HTML document by at least one of loading external content into the HTML document in response to executing the server script, removing the server script from the HTML document, and replacing in the proxy script the proxied function with a proxy; and

a bridge component functionally coupled between the core browser engine and the server framework component configured to send events to the server framework component during defined moments of processing the HTML document by the core browser engine, the events comprising data relevant to the processing of the HTML document, wherein the HTML document is rendered through a web browser executed on the client computer.

2. The server system of claim 1 wherein the HTML document further includes a callback script comprising a callback function and wherein the framework is configured for saving the callback function, which is retrieved and executed when the framework receives a callback request.

3. The server system of claim 1 wherein the server framework further determines if a script has an attribute indicating whether or not the script is to be run on the server.

4. The server system of claim 1 wherein the native language comprises C/C++, and the extensible interpreted language comprises JavaScript.

5. A system comprising:

a web-server system executed on a server computer of a networked computer system, the web-server system comprising;

a HTTP request server,

a handler component in communication with the HTTP request server,

a JavaScript server architecture in communication with the handler component, the JavaScript server architecture comprising;

a core browser engine written in a native language excluding JavaScript or a similar extensible programming a e for parsing an HTML document comprising a server script for execution by a server, and a proxy script including a proxied function, for interpreting the server script and the proxy script, and for creating a DOM corresponding to the HTML document,

a server framework component written in JavaScript or the similar extensible programming language, the framework component comprising a plurality of registered event handlers for performing the business logic of the JavaScript server architecture, and for modifying the DOM corresponding to the HTML document by at least one of loading external content into the HTML document in response to executing the at least one server script, removing the server script from the HTML document, and replacing in the proxy script the proxied function with a proxy, and

a bridge component functionally coupled between the core browser engine and the server framework component configured to send events to the server framework component during defined moments of processing the HTML document by the core browser engine, the events comprising data relevant to the processing of the HTML document, wherein the HTML document is rendered through a web browser executed on a client computer coupled to the server computer.

6. The system of claim 5 wherein the HTML document further includes a callback script comprising a callback function and wherein the framework is configured for saving the callback function, which is retrieved and executed when the framework receives a callback request.

7. A non-transitory computer-readable storage medium with an executable computer program product, which when executed by a server performs a method comprising:

parsing, by a core, an HTML document comprising at least one of a server script for execution by a server and a proxy script including a proxied function, wherein the core is written in a native language different from JavaScript or a similar extensible language;

interpreting, by the core, at least one of the server script and the proxy script;

creating a DOM corresponding to the HTML document; and

modifying, by a framework written in JavaScript or the similar extensible language, the DOM corresponding to the HTML document by at least one of loading external content into the HTML document in response to executing the at least one server script, removing the server script from the HTML document, and replacing in the proxy script the proxied function with a proxy after notifying through a bridge component functionally coupled between the core framework events encountered during defined moments of processing the HTML document by the core browser engine, the events comprising data relevant to the processing of the HTML document.

8. The computer-readable storage medium of claim 7 wherein the HTML document further includes a callback script comprising a callback function and wherein the computer program product further performs saving the callback function, which is retrieved and executed when the server framework component receives a callback request.

9. A method for processing a HTML page on a server, the method comprising:

encountering by a core of a JavaScript architecture an HTML document comprising at least one of a server script for execution by a server and a proxy script including a proxied function, wherein the core is written in a native language excluding JavaScript or a similar extensible programming language;

creating a DOM corresponding to the HTML document;

configuring the core to send events to a framework of the JavaScript architecture during defined moments of processing the HTML document by the core, the events comprising data relevant to the processing of the HTML document wherein the framework is written in JavaScript or the similar extensible programming language;

notifying the framework that an event has occurred through a bridge component functionally coupled between the core browser engine and the server framework component;

inspecting the HTML document by the framework; and

modifying, by the framework, the DOM corresponding to the HTML document by at least one of loading external content into the HTML document in response to executing the at least one server script, removing the server script from the HTML document, and replacing in the proxy script the proxied function with a proxy.

10. The method according to claim 9 wherein:

encountering the HTML document comprises encountering a <

script>

tag in the HTML document.

11. The method according to claim 10 wherein creating a DOM corresponding to the HTML document comprises creating a DOM node corresponding to the <

script>

tag of the HTML document.

12. The method according to claim 11 wherein notifying a framework of the JavaScript architecture that an event has occurred comprises notifying a framework of the JavaScript architecture that a new HTML element event has occurred.

13. The method according to claim 12 wherein inspecting the HTML document by the framework comprising inspecting an associated data of the new HTML element to determine if the tag was a script element.

14. The method according to claim 13 further comprising directing the core pertaining to processing the script element.

15. The method according to claim 13 further comprising directing the core to not process the script element.

16. The method of claim 9 wherein the HTML document further includes a callback script comprising a callback function, the method further including saving the callback function, which is retrieved and executed when the framework receives a callback request.