Adding directives for JavaScript files directly into source code in a multi-tenant database environment
First Claim
1. A method, comprising:
- receiving, at a preprocessor, a source file for preprocessing, wherein the source file is written in a client-side scripting language;
parsing, at the preprocessor, the source file;
identifying, at the preprocessor, a directive within the source file;
associating, at the preprocessor, metadata with the directive during the preprocessing such that the directive is a preprocessed directive, wherein the metadata comprises;
information regarding which portions of the source file have been altered since a last preprocessing of the source file has occurred, and at least a portion of the source file in the client-side scripting language for generating at least a portion of markup language for a web page to be served to a client device using a webserver;
retrieving, during the preprocessing, only the metadata associated with the preprocessed directive in the source file from a database system such that the entire source file is not retrieved;
storing, during the preprocessing, the metadata associated with the preprocessed directive in a hash table;
receiving a request to access metadata associated with the preprocessed directive in the source file from the hash table; and
generating the at least the portion of markup language for the web page to be served to the client device in accordance with the metadata associated with the preprocessed directive in response to the request.
1 Assignment
0 Petitions
Accused Products
Abstract
In a method, system, and computer-readable medium having instructions for adding directives for JavaScript files directly into source code, a source file for preprocessing is received and the source file is written in a client-side scripting language, the source file is parsed, directive information is identified within the source file, metadata is associated with the directive during preprocessing, metadata associated is retrieved with a preprocessed directive, a request to access metadata associated with a preprocessed directive in the source file is received and the preprocessed directive is the directive from the source file, and at least a portion of markup language is generated for a web page in accordance with metadata associated with the preprocessed directive in response to the request.
151 Citations
20 Claims
-
1. A method, comprising:
-
receiving, at a preprocessor, a source file for preprocessing, wherein the source file is written in a client-side scripting language; parsing, at the preprocessor, the source file; identifying, at the preprocessor, a directive within the source file; associating, at the preprocessor, metadata with the directive during the preprocessing such that the directive is a preprocessed directive, wherein the metadata comprises;
information regarding which portions of the source file have been altered since a last preprocessing of the source file has occurred, and at least a portion of the source file in the client-side scripting language for generating at least a portion of markup language for a web page to be served to a client device using a webserver;retrieving, during the preprocessing, only the metadata associated with the preprocessed directive in the source file from a database system such that the entire source file is not retrieved; storing, during the preprocessing, the metadata associated with the preprocessed directive in a hash table; receiving a request to access metadata associated with the preprocessed directive in the source file from the hash table; and generating the at least the portion of markup language for the web page to be served to the client device in accordance with the metadata associated with the preprocessed directive in response to the request. - View Dependent Claims (2, 3, 4, 5, 6, 7, 19, 20)
-
-
8. A non-transitory computer-readable storage medium having one or more instructions thereon, the instructions when executed by one or more processors causing the one or more processors to carry out:
-
receiving a source file for preprocessing, wherein the source file is written in a client-side scripting language; parsing the source file; identifying a directive within the source file; associating metadata with the directive during the preprocessing such that the directive is a preprocessed directive, wherein the metadata comprises;
information regarding which portions of the source file have been altered since a last preprocessing of the source file has occurred, and at least a portion of the source file in the client-side scripting language for generating at least a portion of markup language for a web page to be served to a client device using a webserver;retrieving, during the preprocessing, only the metadata associated with the preprocessed directive in the source file such that the entire source file is not retrieved; storing, during the preprocessing, the metadata associated with the preprocessed directive in a hash table; creating, during the preprocessing, a mapping for the stored metadata associated with the preprocessed directive; receiving, after the parsing, identifying, associating, retrieving, storing, and creating, a request to access metadata associated with the preprocessed directive in the JavaScript source file; and generating the at least the portion of markup language for the web page to be served to the client device in accordance with the metadata associated with the preprocessed directive from the hash table according to the mapping in response to the request. - View Dependent Claims (9, 10, 11, 12)
-
-
13. A system for adding directives for JavaScript files directly into source code, the system comprising:
-
a processor; and one or more stored sequences of instructions which, when executed by the processor, cause the processor to carry out; receiving a source file for preprocessing, wherein the source file is written in a client-side scripting language; parsing the source file; identifying a directive within the source file; associating metadata with the directive during the preprocessing such that the directive is a preprocessed directive, wherein the metadata comprises;
information regarding which portions of the source file have been altered since a last preprocessing of the source file has occurred, and at least a portion of the source file in the client-side scripting language for generating at least a portion of markup language for a web page to be served to a client device using a webserver;retrieving, during the preprocessing, only the metadata associated with the preprocessed directive in the source file such that the entire source file is not retrieved; storing, during the preprocessing, the metadata associated with the preprocessed directive in a hash table; creating, during the preprocessing, a mapping for the stored metadata associated with the preprocessed directive; receiving, after the parsing, identifying, associating, retrieving, storing, and creating, a request to access the metadata associated with the preprocessed directive in the source file; and generating the at least the portion of markup language for the web page to be served to the client device in accordance with the metadata associated with the preprocessed directive from the hash table according to the mapping in response to the request. - View Dependent Claims (14, 15, 16, 17, 18)
-
Specification