Adding directives for versions of javascript files directly into source code in a multi-tenant database environment

• US 9,262,137 B2
• Filed: 01/05/2011
• Issued: 02/16/2016
• Est. Priority Date: 05/27/2010
• Status: Active Grant

• Current Assignee: Salesforce.com, Inc.
• Original Assignee: Salesforce.com, Inc.
• Inventors: Mooney, James
• Primary Examiner(s): BROPHY, MATTHEW J
• Application Number:
  US12/985,298
• Publication Number:
  US 20110296381A1
• Time in Patent Office: 1,868 Days
• Field of Search: 717/136
• US Class Current: 1/1
• CPC Class Codes: G06F 8/423 Preprocessors
• CPC Class Codes: G06F 8/658 Incremental updates; Differential updates
• CPC Class Codes: G06F 8/71 Version control security arrangements therefor G06F21/57; Configuration management
• CPC Class Codes: G06F 9/45516 Runtime code conversion or optimisation

Abstract

In a method, system, and computer-readable medium having instructions for adding directives for versions of 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 for a directive within the source file and the directive information comprises data on at least a portion of a client-side scripting language file and a mode, a version of the source file for the mode is created and the version of the source file comprises source code from the source file and the at least a portion of the client-side scripting language file, and metadata is associated with the directive and the version of the source file.

Claims

1. A method, comprising:

receiving, at a processor, a source file for preprocessing, wherein the source file comprises source code and is written in a client-side scripting language;

parsing, at the processor, the source file;

identifying, at the processor, directive information for a preprocessed directive within the source code of the source file, wherein the directive information comprises data on at least a portion of a client-side scripting language file and a mode;

creating, at the processor, a version of the source file for the mode, wherein the version of the source file comprises the source code from the source file and the at least a portion of the client-side scripting language file;

associating, at the processor, metadata with the preprocessed directive and the version of the source file, 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 client-side scripting language file for generating at least a portion of markup language for a web page to be served to a client device using a webserver;

storing the metadata in a database;

retrieving, via the webserver from the database, only the metadata associated with the preprocessed directive in the version of the source file such that the entire source file is not retrieved; and

in response to receiving a request for the metadata associated the version of the source file, generating, in accordance with the metadata associated with the preprocessed directive and the version of the source file, at least the portion of the markup language for the web page to be served to the client device.

2. The method of claim 1, wherein retrieving comprises:

retrieving, at the webserver from the database, only the metadata associated with the preprocessed directive from the source code from the source file that is also included in the version of the source file.

3. The method of claim 1, wherein the mode comprises at least one of debug, development, production, test, and performance test.

4. The method of claim 1, wherein the data on at least a portion of the client-side scripting language file comprises a file path for a directory.

5. The method of claim 1, wherein the version of the source file comprises JavaScript for one or more groups.

6. The method of claim 5, wherein the metadata for the version of the source file comprises a URL for a group from the one or more groups.

7. The method of claim 1, wherein the directive comprises at least one of an include directive and an if directive.

8. A non-transitory computer-readable storage medium having one or more instructions thereon for adding directives for versions of JavaScript files directly into source code, the instructions when executed by one or more processors causing the one or more processors to carry out:

receiving, at one of the processors, a source file for preprocessing, wherein the source file comprises source code and is written in a client-side scripting language;

parsing, at one of the processors, the source file;

identifying, at one of the processors, directive information for a preprocessed directive within the source code of the source file, wherein the directive information comprises data on at least a portion of a client-side scripting language file and a mode;

creating, at one of the processors, a version of the source file for the mode, wherein the version of the source file comprises the source code from the source file and the at least a portion of the client-side scripting language file;

associating, at one of the processors, metadata with the preprocessed directive and the version of the source file, 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 client-side scripting language file for generating at least a portion of markup language for a web page to be served to a client device using a webserver;

storing, via one of the processors, the metadata in a database;

retrieving, via one of the processors that is implemented at the webserver from the database, only the metadata associated with the preprocessed directive in the version of the source file such that the entire source file is not retrieved; and

in response to receiving a request for the metadata associated the version of the source file, generating, at one of the processors in accordance with the metadata associated with the preprocessed directive and the version of the source file, at least the portion of the markup language for the web page to be served to the client device.

9. The non-transitory computer-readable storage medium of claim 8, wherein retrieving comprises:

retrieving, via one of the processors that is implemented at the webserver from the database, only the metadata associated with the preprocessed directive from the source code from the source file that is also included in the version of the source file.

10. The non-transitory computer-readable storage medium of claim 8, wherein the mode comprises at least one of debug, development, production, test, and performance test.

11. The non-transitory computer-readable storage medium of claim 8, wherein the data on at least a portion of the client-side scripting language file comprises a file path for a directory.

12. The non-transitory computer-readable storage medium of claim 8, wherein the version of the source file comprises JavaScript for one or more groups.

13. The non-transitory computer-readable storage medium of claim 8, wherein the metadata for the version of the source file comprises a URL for a group from the one or more groups.

14. A system for adding directives for versions of JavaScript files directly into source code, the system comprising:

a first processor;

a webserver;

a database; and

one or more stored sequences of instructions which, when executed by the first processor, cause the first processor to carry out;

receiving, at the first processor, a source file for preprocessing, wherein the source file comprises source code and is written in a client-side scripting language;

parsing, at the first processor, the source file;

identifying, at the first processor, directive information for a preprocessed directive within the source code of the source file, wherein the directive information comprises data on at least a portion of a client-side scripting language file and a mode;

creating, at the first processor, a version of the source file for the mode, wherein the version of the source file comprises the source code from the source file and the at least a portion of the client-side scripting language file;

associating, at the first processor, metadata with the preprocessed directive and the version of the source file, 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 client-side scripting language file for generating at least a portion of markup language for a web page to be served to a client device using a webserver;

storing the metadata in the database;

wherein the webserver is configured to;

retrieve, from the database, only the metadata associated with the preprocessed directive in the version of the source file such that the entire source file is not retrieved; and

in response to receiving a request for the metadata associated the version of the source file, generate, in accordance with the metadata associated with the preprocessed directive and the version of the source file, at least the portion of the markup language for the web page to be served to the client device.

15. The system of claim 14, wherein the

webserver is configured to retrieve, from the database, only the metadata associated with the preprocessed directive from the source code from the source file that is also included in the version of the source file.

16. The system of claim 14, wherein the mode comprises at least one of debug, development, production, test, and performance test.

17. The system of claim 14, wherein the data on at least a portion of the client-side scripting language file comprises a file path for a directory.

18. The system of claim 14, wherein the version of the source file comprises JavaScript for one or more groups.

19. The system of claim 14, wherein the directive comprises at least one of an include directive and an if directive.

20. The system of claim 14, wherein the metadata for the version of the source file comprises a URL for a group from the one or more groups.