String template pages for generating HTML document

• US 20050235200A1
• Filed: 06/15/2005
• Published: 10/20/2005
• Est. Priority Date: 10/30/2000
• Status: Active Grant

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Goldberg, Matthew A.
• Granted Patent: US 7,376,892 B2
• Time in Patent Office: Days
• US Class Current: 715/256
• CPC Class Codes: G06F 16/958 Organisation or management of web site content, e.g. publishing, maintaining pages or automatic linking

Abstract

A system and method is provided for generating dynamically changing HTML documents at a relatively quick rate in response to a client request. The system and method provide separation of the constant text and the code embedded in the HTML documents. An executable component is employed that includes all the basic functionality typically embedded in script code of a plurality of HTML documents. The dynamically generated text is broken down into string template pages. Each string template page can be authored as a single file and includes all the information necessary to complete a request. A string template page includes one or more strings and each string is made up of a text constant and can include one or more argument variables. Each string template page is provided with identifiers for pages, text constants and variable portions of strings. The pages are read, parsed and processed into a data structure into memory by the executable component for efficient use at runtime.

Claims

1. A system for servicing a client request comprising:

an executable component that receives the request and executes code corresponding to the request, the executable component retrieves at least one text constant and inserts at least one variable argument result corresponding to the request into the at least one text constant, the executable component passes the at least one text constant to the client.

2. The system of claim 1, wherein the at least one text constant and the variable argument result reside in a memory location accessible by the executable component.

3. The system of claim 1, wherein the at least one text constant and the variable argument result are loaded into memory prior to runtime.

4. The system of claim 1, further comprising at least one string template page having at least one text constant.

5. The system of claim 4, the at least one string template page having at least one argument associated therewith.

6. The system of claim 4, the at least one text constant having at least one argument associated therewith.

7. The system of claim 6, the at least one text constant employing a new string indicator to identify each of the at least one text constant and a new argument indicator to identify each of the at least one argument.

8. The system of claim 4, the executable component loading the at least one string template page and parsing the at least one string template page to identify the at least one text constant, the executable component storing the at least one text constant into memory and retaining a unique identifier of the at least one text constant for retrieving the at least one text constant from memory at runtime.

9. The system of claim 8, the executable component also retaining a pointer to the memory location of the at least one text constant for retrieving the at least one text constant from memory at runtime.

10. The system of claim 8, the executable component parsing the at least one text constant to identify at least one argument associated with the at least one text constant, the executable component retaining a unique identifier number for the at least one argument for retrieving the at least one variable argument result at runtime.

11. The system of claim 10, the executable component also retaining a pointer to a location of the at least one argument within the at least one text constant for determining the location for inserting the at least one variable argument result into the at least one text constant at runtime.

12. The system of claim 8, further comprising a monitoring system for informing the executable component of any changes occurring in the at least one string template page, the executable component reloads, parses and stores the changed at least one string template page upon being informed of any changes by the monitoring system.

13. The system of claim 12, the monitoring system being a configuration data source.

14. The system of claim 1, the executable component employing at least one intelligent ID to retrieve the at least one text constant from memory.

15. The system of claim 1, the at least one text constant being an HTML text constant.

16. A computer readable medium having computer-executable components comprising;

a first component receiving a request from a client and executing code corresponding to the request, the first component retrieving at least one text constant residing in a memory corresponding to the request, the first component retrieving at least one variable argument result from the memory corresponding to the request and inserting the at least one variable argument result into the at least one text constant, and the first component inserting the at least one text constant into a file and passing the file to the client.

17. The computer readable medium of claim 16, further comprising at least one string template page, the first component further parsing the at least one string template page for the at least one text constant and storing the at least one text constant in the memory.

18. The computer readable medium of claim 16, further comprising a second component that monitors any changes in the at least one string template page and informs the first component of any changes in the at least one string template page.

19. The computer readable medium of claim 18, the first component parsing the changed at least one string template page for a changed at least one text constant upon being informed of any changes by the second component, the first component storing the changed at least one text constant in memory in place of the at least one text constant.

20. A client request servicing system, comprising:

means for receiving the request and executing code corresponding to the request, means for retrieving at least one text constant

means for inserting at least one variable argument result corresponding to the request into the at least one text constant

means for passing the at least one text constant to the client.