KR19990040514A - How to create CGI program automatically - Google Patents

Abstract

The present invention relates to a method for automatically generating a common gateway interface (CGI) program, and more particularly, to a method for automatically generating a CGI program that enables the authoring of a web document dynamically generated according to a client's request. Its purpose is to create dynamic web documents quickly and simply by automatically generating CGI programs by combining information about HTML interfaces designed by developers under the web authoring environment and information about search conditions entered by users accessing websites. It's about letting go. In the CGI program automatic generation method for automatically generating a CGI program that outputs a search result according to a specified HTML format, the first step of analyzing the user input information, and the analysis of the input information and the SQL template A second step of generating a complete SQL code using information; a third step of executing the generated SQL code; and a fourth step of analyzing the SQL code execution result and information of an HTML template to generate HTML code. It's there.

Description

How to create CGI program automatically

The present invention relates to a method for automatically generating a common gateway interface (CGI) program, and more particularly, to a method for automatically generating a CGI program that enables the authoring of a web document dynamically generated according to a client's request.

In general, CGI is a type of convention interface for HyperText Transport Protocol (HTTP) servers and resources within the server, as well as information transfer methods and variables that the server and the client exchange with each other. Allows you to generate documents dynamically. In addition, the types of web documents can be largely classified into static documents and dynamic documents. Static documents are documents that are displayed in the same form to all users in all situations once designed. A document whose contents or form change according to the user's choice. Dynamic documents are generated using CGI programs. CGI programs are designed to accept user input, search a database by executing a query, and output search results according to the syntax of HTML (HyperText Markup Language) tags. Functions for output types are included. CGI program with this function can be used to search the database for data that meet the conditions of the connection and output the result.The document created by this process is a dynamic document, It serves to provide information.

Conventional web authoring tools support the authoring of static web documents by providing an HTML tag icon, a visualization of user access, and a web document design technique using the WYSIWYG (What You See Is What You Get) method. However, such a conventional web authoring tool does not support authoring of a web document dynamically generated by a client request. Therefore, a developer must design and code a CGI program for generating a dynamic web document entirely by the developer. There was this. In addition, such a conventional web authoring tool requires a developer to write a CGI program for generating a dynamic document. Therefore, the developer must not only know the CGI programming technique, but also a database such as HTML tagging scheme and structured query language (SQL). There is a problem that it takes a lot of time to write a CGI program for dynamic document generation because it requires knowledge of language syntax, database search method and procedure.

The present invention devised to improve the problems of the existing authoring method as described above by combining the information on the HTML interface designed by the developer in the web authoring environment and the search conditions entered by the user accessing the web site The goal is to enable dynamic Web document authoring quickly and simply by automatically generating CGI programs.

In order to achieve the above object, the system of the present invention includes a visual editor, a CGI generator, and a program generated by the CGI generator includes an analyzer and a code generator, wherein the analyzer is a module for analyzing a user's input generated during web access. And a module for analyzing a SQL template and an HTML template. The code generator includes a module for generating SQL code, a module for executing SQL code, and an HTML code generation module for executing a query. In addition, a generation module for setting CGI code execution information using environment setting information is provided.

A feature of the present invention for achieving the above object is a CGI program automatic generation method for automatically generating a CGI program for outputting a search result according to a specified HTML format, the first step of analyzing the user input information, and A second step of generating a complete SQL code using the analyzed input information and the information of the SQL template, a third step of executing the generated SQL code, and a result of analyzing the SQL code execution result and information of the HTML template and the HTML code Including a fourth step of generating a. In this case, the first step includes a process of inputting information through a form by a user during web access, a process of analyzing the input information, and an analysis of environmental information, or a user at web access. The method includes selecting an anchor, analyzing the information of the selected anchor, and analyzing the environmental information. The fourth step is a first step of performing a filtering operation for determining which part of the result of the third step to provide as a web document, and outputting the token until the token of 'ListTable' is returned. A second step of reading a template file in token units, a third step of reading a token from the HTML template while outputting a corresponding output value according to the type of the token until a token of 'End' appears, and a 'PreNext' A fourth process of reading a token from the HTML template while outputting a token until an in token appears, and a fifth process of reading a token from the HTML template while generating anchor information until an 'End' token comes out And a sixth process of reading a token from the HTML template until the end of the HTML template file comes out. The second step may include a first step of reading the HTML template file in token units, a second step of determining whether a token is a 'ListTable', and if it is determined that the token is not a 'ListTable' in the second step, A third step of reading a token from the HTML template, a fourth step of outputting a token and proceeding to the first step, and reading the token from the HTML template if it is determined that the token is 'ListTable' in the second step. It consists of 5 steps. The third step may include: a first step of determining whether the token type is a variable; a second step of outputting a value corresponding to a result of performing SQL to a standard output device when it is determined that the token type is a variable in the first step; If it is determined in step 1 that the token type is not a variable, a third step of outputting the token to a standard output device; a fourth step of reading the token from the HTML template; and a fifth step of determining whether the token is 'End'. If it is determined in the step and the fifth step that the token is not 'End', the sixth step proceeds to the first step. The fourth step includes a first step of reading a token from the HTML template, a second step of determining whether it is the end of the HTML template file, and a third step of ending if the end of the HTML template file is determined in the second step; If it is determined that the end of the HTML template file is not the end of the HTML template file in the second step, the fourth step determines whether the token is 'PreNext', and if it is determined in the fourth step that the token is not 'PreNext', the process proceeds to the first step. If it is determined that the token is 'PreNext' in the fifth step and the fourth step, a sixth step of reading the token from the HTML template is performed. The fifth process includes a first step of obtaining the URL information, a second step of generating the anchor information, a third step of reading a token from the HTML template, and a fourth step of determining whether the token is 'End'. And a fifth step proceeding to the first step if it is determined that the token is not 'End' in the fourth step. The anchor information is composed of the URL and the argument list, and the URL is composed of a specific syntax for expressing various information about the resource such as a host computer name and path information where the resource is located, and the argument list is located in the URL. When calling a CGI program, it is used to pass a pair of program arguments and their values. The sixth step includes a first step of reading a token from the HTML template, a second step of determining whether the end of the HTML template file is the end, and if it is determined in the second step that the HTML template file is not the end, the token is output to the standard output device. If it is determined that the HTML template file is the end in the third step and the second step to output the first step and the second step, the fourth step to end.

The present invention analyzes the template information corresponding to the information input by the user and the skeleton information on the SQL and HTML described by the developer to complete the SQL code to meet the user's requirements at the time of accessing the web site and specify the developer. Automatically generate CGI programs that dynamically generate web documents by outputting SQL code execution results to conform to HTML code structure.

1 is a conceptual diagram of a CGI function.

2 is an overall configuration diagram of a system according to the present invention.

3 is a configuration diagram of a CGI program.

4A-4C are data flow diagrams for dynamic HTML code generation.

5A to 5C are data flow diagrams for generating SQL code.

Hereinafter, with reference to the accompanying drawings will be described in detail one of the preferred embodiments according to the present invention.

1 is a conceptual diagram of a CGI function. A CGI function will be described with reference to FIG. 1 as follows.

First, the client 20 may navigate through web documents in the web server 11 through the web browser 21 and select or retrieve necessary information to receive the result. CGI is a kind of convention interface for HTTP server and various resources in the server, and the information transmission method and variables that the server 10 and the client 20 exchange with each other, and meet the requirements at the moment that the client 20 requests. Allows you to dynamically generate documents. While the CGI executable file is stored in a specific directory of the web server 11, when a call from the web server 11 occurs, the CGI executable file is connected to the web database application server 12 to perform a database processing operation such as a search and the like. It serves to pass back to the web server (11).

2 is an overall configuration diagram of a system according to the present invention. Referring to Figure 2 describes the overall configuration of the system according to the present invention.

The system according to the invention consists of a visual editor 30 and a CGI generator 40. The visual editor 30 first provides an HTML template generator 32, which is a document that combines static HTML code and macro definitions of information to be changed dynamically. The module supports WYSIWYG web document authoring using icons to easily design the output format so that web documents can be dynamically generated according to the search results of a database that satisfies the user's requirements for web access. To be able. As a result, developers can easily design dynamic Web documents in a visual development environment without requiring any additional knowledge of HTML tags. In addition, the visual editor 30 provides a SQL template generator 31 to provide a query generation function. When a developer selects a field to be used for a field and condition to be searched in the database with a mouse, a corresponding SQL template is generated so that it can be combined with the condition entered by the user when connecting to the web. The CGI generator 40 analyzes the information about the templates, information about each template related to which of the documents to be authored, and system configuration information, and combines the basic packages provided by the system of the present invention. Automatically generate CGI programs that meet the developer's web authoring needs.

3 is a block diagram of a CGI program. Referring to Figure 3 describes the structure of the CGI program generated using the packages provided by the system of the present invention as follows.

The program generated by the system of the present invention is largely composed of an analyzer 70 and a code generator 80. The analyzer 70 includes a user input analysis module 71, an SQL template analysis module 72, and an HTML template analysis module 73. The SQL template analysis module 72 analyzes the information of the SQL template generated by the visual editor 30 to extract information necessary for generating SQL, and the HTML template analysis module 73 generates the HTML generated by the visual editor 30. Analyze the information in the template to analyze the information about the parts that can be used statically and the parts that need to be generated dynamically in combination with the database search results. The user input analysis module 71 decodes and analyzes information of parameters input through a form while the user is connected to the web so that the user input analysis module 71 can be used for generating SQL code and HTML code. The code generator 80 passes through the SQL code generation module 81, the SQL query execution module 82, and the HTML code generation module 83. The SQL code generation module 81 first generates a complete SQL code using a user input and SQL template analysis information. In addition, the SQL query execution module 82 performs a generated SQL code to search a database. In addition, the HTML code generation module 83 combines the search results of the SQL query execution module 82 and the HTML template information to dynamically generate a document to be displayed to the user when the web is connected.

4A-4C are data flow diagrams for dynamic HTML code generation. Referring to Figures 4a to 4c describes the flow of data for dynamic HTML code generation as follows.

First, in S1, a user enters information through a form during web connection. However, the user may select an anchor as in S2 without entering information. In S3, the information input by the user through the form in S1 or the anchor information selected by the user in S2 is analyzed. Then, in S4, the environmental information is analyzed. S5 generates complete SQL code using the analyzed information and the SQL template. In S6, execute the SQL code. In operation S7, a filtering operation for determining which part of the result of S6 to provide as a web document is performed. In S8, HTML template files are read in token units. In S9, it is determined whether the token is a 'ListTable' or not. If it is determined in S9 that the token is not 'ListTable', in S10, the token is read from the HTML template. In S11, the token is output and the HTML template file is read again in S8. If it is determined in S9 that the token is a 'ListTable', since the search result has information on what format it should be outputted, the token is read from the HTML template in S12. This is done by reading the HTML template file and processing it in token units. It determines the part where the part of the template is statically used and dynamically changed by the query search result. The static part is information that appears irrespective of the query search result, and the part that needs to be dynamically generated is the part that outputs the search result in a specified format and the anchors having the page information generated by it. In S13, it is determined whether the token type is a variable. If it is determined in step S13 that the type of the token is a variable, in S14 the value corresponding to the SQL execution result is output to the standard output device. However, if it is determined in S13 that the type of the token is not a variable, in S15 the token is output to the standard output device. After performing S14 or S15, S16 reads the token from the HTML template. In S17, it is determined whether the token is 'End'. If it is determined in S17 that the token is not 'End', it is determined again in S13 whether the token type is a variable. However, if the token is determined to be 'End' in S17, the token is read from the HTML template in S18. In S19, it is determined whether the end of the HTML template file. If it is determined in S19 that the end of the HTML template file, it ends. If it is determined in step S19 that the HTML template file is not the end, in step S20 it is determined whether the token is 'PreNext'. If it is determined in step S20 that the token is not 'PreNext', the token is read from the HTML template again in step S18. If it is determined in step S20 that the token is 'PreNext', the token is read from the HTML template in S22. That is, the above processes are to analyze the tokens of the search results and HTML templates and combine them with the query execution results to generate dynamic documents. Then, if the number of items to be displayed as a search result is larger than the number to be printed on one page, if the output is to be divided into several pages, the previous page and next page anchor information for this should be generated. This occurs when the token 'PreNext' appears in the SQL template. The anchor information that should be described on the previous and following pages is a Uniform Resource Locator (URL) and a list of arguments. The URL consists of a specific syntax that represents a variety of information about the resource, such as the host computer name and path information where the resource is located. The argument list is used to pass a pair of program arguments and their values when calling a CGI program at the URL. Therefore, URL information is obtained in S23, and anchor information is generated in S24. In S25, the token is read from an HTML template. In S26, it is determined whether the token is 'End'. If it is determined in S26 that the token is not 'End', URL information is obtained in S23. However, if the token is determined to be 'End' in S26, the token is read from the HTML template in S27. In S28, it is determined whether the end of the HTML template file. If it is determined in step S28 that the HTML template file is not the end, in S29 the token is output to the standard output device, and in step S27, the token is read from the HTML template. If it is determined in step S28 that the HTML template file is finished, the process ends.

5A to 5C are data flow diagrams for generating SQL code. Referring to Figures 5a-5c, the data flow for generating the SQL code is as follows.

First, in S31, the SQL template is read in token units. Thereafter, in S32 to S52, a corresponding syntax is generated depending on whether the token is 'Select', 'From' or 'Where'. That is, in S32, it is determined whether the token is 'Select'. If it is determined in S32 that the token is not 'Select', then S38 determines whether the token is 'From'. If it is determined in S38 that the token is not 'From', it is determined in S44 whether the token is 'Where'. If it is determined in S44 that the token is not 'Where', an error message is generated and terminated in S45. If it is determined in S32 that the token is 'Select', then S33 outputs the token to a standard output device. In S34, information about which field of the database is searched for is obtained from the argument information or the anchor information of the form. At this time, a list of fields is generated in accordance with the 'Select' statement. In addition, the print information of the form refers to information generated by the user setting the elements of the form in the web document including the form. In S35, the extracted information is output to the standard output device. In S36, the SQL template is read in token units. In S37, it is determined whether the token is 'From'. If it is determined in S37 that the token is not 'From', the token is output to the standard output device in S33. If it is determined in S37 or S38 that the token is 'From', S39 outputs the token to a standard output device. In S40, the configuration information is analyzed to obtain the name and information of the database to be searched. In S41, the extracted information is output to the standard output device. In S42, SQL templates are read in token units. In S43, it is determined whether the token is 'Where'. If it is determined in S43 that the token is not 'Where', the token is output to the standard output device in S39. If it is determined in S43 or S44 that the token is 'Where', S46 outputs the token to a standard output device. In S47, SQL templates are read in token units. In S48, it is determined that the end of the SQL template file. If it is determined that the end of the SQL template file in step S48, it ends. If it is determined in S48 that it is not the end of the SQL template file, in S49 the information corresponding to the query condition is extracted by analyzing the information or anchor information input by the user in the form. In S50, it is determined whether other conditions exist. If it is determined in S50 that another condition exists, in S51, the form may query with multiple values for the same field, and then analyze whether there is an AND or OR condition and combine the condition description part of the SQL template with the conditions. Generate a complete conditional statement. After the execution of S51 or when it is determined that no other condition exists in S50, in S52, the extracted conditional statement is output to the standard output device, and in S47, the SQL template is read in token units.

The present invention facilitates the generation of HTML code for dynamic web documents, allows developers to create CGI programs simply and quickly, even if they are not familiar with CGI programs, and to present a variety of dynamic information provided by generating dynamically flexible HTML code. The effect is to facilitate this.

Claims (9)

In the CGI program automatic generation method that automatically generates a CGI program that outputs the search results according to the specified HTML format, A first step of analyzing user input information; A second step of generating a complete SQL code by using the analyzed input information and information of an SQL template; A third step of executing the generated SQL code; And And a fourth step of generating the HTML code by analyzing the SQL code execution result and the information on the HTML template. The method of claim 1, The first step, Inputting information through a form when a user accesses a web; Analyzing the input information; And Method for automatically generating a CGI program, characterized in that consisting of the process of analyzing the environmental information. The method of claim 1, The fourth step, A first step of performing a filtering operation to determine which part of a result of the third step to provide as a web document; A second step of reading the HTML template file in token units while outputting the token until a token that is 'ListTable' is obtained; A third step of reading a token from the HTML template while outputting a corresponding output value according to the type of the token until a token of 'End' is obtained; A fourth step of reading the token from the HTML template while outputting the token until a token of 'PreNext' is obtained; A fifth step of reading the token from the HTML template while generating anchor information until a token of 'End' is issued; And And a sixth step of reading the token from the HTML template until the end of the HTML template file. The method of claim 3, wherein The second process, A first step of reading the HTML template file in token units; A second step of determining whether the token is a 'ListTable' or not; A third step of reading the token from the HTML template if it is determined in the second step that the token is not 'ListTable'; A fourth step of outputting a token and proceeding to said first step; And If it is determined that the token is 'ListTable' in the second step, CGI program automatic generation method comprising the step of reading the token from the HTML template. The method of claim 3, wherein The third process, A first step of determining whether the token type is a variable; A second step of outputting a value corresponding to a result of performing SQL to a standard output device when it is determined that the token type is a variable in the first step; A third step of outputting the token to a standard output device if it is determined in the first step that the type of the token is not a variable; A fourth step of reading a token from the HTML template; A fifth step of determining whether the token is 'End'; And And if it is determined that the token is not 'End' in the fifth step, the CGI program automatic generation method comprising: a sixth step proceeding to the first step. The method of claim 3, wherein The fourth process, A first step of reading a token from the HTML template; A second step of determining whether it is an end of an HTML template file; Terminating if it is determined that the HTML template file is the end in the second step; A fourth step of determining whether the token is 'PreNext' if it is determined that the end of the HTML template file is not the end in the second step; A fifth step of proceeding to the first step if it is determined in the fourth step that the token is not 'PreNext'; And If it is determined in step 4 that the token is 'PreNext', CGI program automatic generation method comprising the step of reading the token from the HTML template. The method of claim 3, wherein The fifth process, A first step of obtaining the URL information; A second step of generating the anchor information; A third step of reading a token from the HTML template; A fourth step of determining whether the token is 'End'; And And if it is determined that the token is not 'End' in the fourth step, the CGI program automatic generation method comprising: a fifth step proceeding to the first step. The method according to claim 3 or 7, The anchor information consists of the URL and the argument list; The URL consists of a specific syntax representing various information about the resource, including the host computer name and path information of where the resource is located; And the argument list is used to pass pairs of program arguments and their values when calling the CGI program at the URL. The method of claim 3, wherein The sixth process, A first step of reading a token from the HTML template; A second step of determining whether it is an end of an HTML template file; A third step of outputting a token to a standard output device if it is determined that the HTML template file is not over in the second step, and proceeding to the first step; And And a fourth step of terminating if the HTML template file is determined to be the end in the second step.