Display control apparatus, display control program and display control method
6 claims: 5 independent, 1 dependent
- 1クライアントからのCGI要求を受信してCGI処理を行ないCGI処理結果を出力するCGI処理部と、 前記CGI要求に基づいて、 前記CGI処理結果に基づく所定の情報を含むと共に、前記クライアントが前記CGI要求を行なうために接続したアドレスと異なる前記リンクアドレスに前記クライアントを接続させるための第1の識別子を含むソースコードを生成し、前記クライアントに送信する アドレス変更部と、 前記アドレス変更部により送信されたソースコードを実行して接続した前記クライアントに対して、前記第1の識別子を、前記所定の情報を前記クライアントにおいて表示させるための第2の識別子に書き換え、前記所定の情報を前記クライアントにおいて表示させる 出力部と を備えてなる表示制御装置。
- 2請求項 1 に記載の表示制御装置において、 前記第1の識別子は、さらに前記 CGI処理部により受信されたCGI要求をした クライアントにおいて前記所定の情報の表示処理をスキップさせることを特徴とする表示制御装置。
- 3請求項 1または 請求項 2に 記載の表示制御装置において、 前記クライアントはインタプリタ言語が実行可能なWebブラウザであることを特徴とする表示制御装置。
- 4クライアントからのCGI要求を受信してCGI処理を行ないCGI処理結果を出力するCGI処理ステップと、 前記CGI要求に基づいて、 前記CGI処理結果に基づく所定の情報を含むと共に、前記クライアントが前記CGI要求を行なうために接続したアドレスと異なる前記リンクアドレスに前記クライアントを接続させるための第1の識別子を含むソースコードを生成し、前記クライアントに送信する アドレス変更ステップと、 前記アドレス変更ステップにより送信されたソースコードを実行して接続した前記クライアントに対して、前記第1の識別子を、前記所定の情報を前記クライアントにおいて表示させるための第2の識別子に書き換え、前記所定の情報を前記クライアントにおいて表示させる 出力ステップと をコンピュータに実行させる表示制御プログラム。
- 5請求項4に記載の表示制御プログラムにおいて、 前記第1の識別子は、さらに前記 CGI処理ステップにより受信されたCGI要求をした クライアントにおいて前記所定の情報の表示処理をスキップさせることを特徴とする表示制御プログラム。
- 6クライアントからのCGI要求を受信してCGI処理を行ないCGI処理結果を出力するCGI処理ステップと、 前記CGI要求に基づいて、 前記CGI処理結果に基づく所定の情報を含むと共に、前記クライアントが前記CGI要求を行なうために接続したアドレスと異なる前記リンクアドレスに前記クライアントを接続させるための第1の識別子を含むソースコードを生成し、前記クライアントに送信する アドレス変更ステップと、 前記アドレス変更ステップにより送信されたソースコードを実行して接続した前記クライアントに対して、前記第1の識別子を、前記所定の情報を前記クライアントにおいて表示させるための第2の識別子に書き換え、前記所定の情報を前記クライアントにおいて表示させる 出力ステップと を備える表示制御方法。
Independent claims6
42 paragraphs, as filed
The present invention relates to a display control device, a display control program, and a method for connecting a Web browser to a different address after processing a CGI request from the Web browser on the Web server.
CGI (Common Gateway Interface) is known as an interface for executing user programs on a Web server. CGI is a program placed on the server. It processes according to the CGI request from the web browser, and the web browser displays the HTML output by the program so that the client can display the processing result on the web browser. What you can see above.
As a related prior art of the present invention, there is known a method of avoiding double transmission from a business HTML screen on a Web browser (see, for example, Patent Document 1).<patcit num="1"><text>Japanese Unexamined Patent Publication No. 2001-229103</text></patcit>
<p> However, since accessing the file in which the CGI program is written itself makes a CGI request, if an update is made on the Web browser after the program is executed, the same CGI request will be issued to the Web server again. This may cause problems that cause multiple processing on the Web server side.</p><p> Also, in order to avoid the above trouble, even if you try to check the CGI request on the Web server side and perform processing that returns an error, if normal processing and abnormal processing are mixed in the CGI request, the Web server is normal. In some cases, it may not be possible to determine whether or not to process.</p><p> Hereinafter, specific examples of malfunctions caused by CGI requests due to the update of the Web browser will be described with reference to FIGS. 8 and 9.</p><p> FIG. 8 is a diagram showing a screen of a Web browser that controls the power on / off of a specific computer, and FIG. 9 is a flow showing a malfunction due to careless update of a user in computer control by the Web browser. In FIG. 8, it is assumed that Web browser A and Web browser B, which are different Web browsers, perform Of / Off control of the power supply to the computer, and the computer is turned on in the initial state.</p><p> First, Web browser A makes a power off request to the computer controlled by the Web-UI (Web-User Interface) output by the CGI program as shown in Fig. 8 by clicking the Off button (S101). ), With the computer turned off, Web browser B makes a power on request to the computer by clicking the On button using the Web-UI in the same way as Web browser A (S102).</p><p> Next, Web browser A makes a power-off request (S103), and then Web browser B makes a power-on request (S104). Then, the Web browser A updates the CGI that has requested the power off, and the Web browser A accesses the CGI while holding the power off request in step S103. As a result, the power off request is made (S105). ).</p><p> As described above, in the conventional method, the computer controlled by the careless update by the user who operates the Web browser determines the update as recontrol and causes a malfunction.</p><p> The present invention has been made to solve the above-mentioned problems, and an object of the present invention is to provide a display control device, a display control program, and a method capable of preventing recontrol of CGI by updating a Web browser.</p>
<p> In order to solve the above-mentioned problems, the display control device according to the present invention has a CGI processing unit that receives a CGI request from a client, performs CGI processing, and outputs a CGI processing result, and the client based on the CGI request. The CGI output by the CGI processing unit to the client whose connection destination has been changed by the address change unit and the address change unit that connect to an address different from the link address connected to make the CGI request. It is provided with an output unit that outputs display information for displaying predetermined information based on the processing result.</p><p> Further, in the display control program according to the present invention, the client makes the CGI request based on the CGI processing step of receiving the CGI request from the client, performing the CGI processing, and outputting the CGI processing result, and the CGI request. A predetermined address based on the CGI processing result output in the CGI processing step for the client whose connection destination has been changed by the address change step of connecting to a link address different from the connected address for the purpose and the address change step. It causes a computer to perform an output step of outputting display information for displaying information.</p><p> Further, in the display control method according to the present invention, the client makes the CGI request based on the CGI processing step of receiving the CGI request from the client, performing the CGI processing, and outputting the CGI processing result, and the CGI request. A predetermined address based on the CGI processing result output in the CGI processing step for the client whose connection destination has been changed by the address change step of connecting to a link address different from the connected address for the purpose and the address change step. It executes an output step that outputs display information for displaying information.</p>
<p> According to the present invention, a display control device and display control that can prevent CGI re-control by updating the Web browser by connecting the Web browser to a different address after processing the CGI request from the Web browser on the Web server. Programs and methods can be provided.</p>
Hereinafter, embodiments of the present invention will be described with reference to the drawings.
Embodiment 1. First, the configuration of the present embodiment will be described.
FIG. 1 is a block diagram showing the overall configuration of the first embodiment, and FIG. 2 is a diagram showing the source code of the link HTML. In addition, FIG. 3 is a diagram showing the source code of the display HTML. In the first embodiment, the power supply of the computer is controlled by the Web-UI as shown in FIG.
As shown in FIG. 1, the Web server 1 has a CGI directory 11 and an HTML directory 12, and the control CGI 111 (CGI processing unit, address change unit, source code generation unit) and display CGI 112 (output unit) are located in the CGI directory 11. It has been saved. In addition, the display HTML 121 is saved in the HTML directory 12.
The source code of the link HTML111a described later is written in the control CGI111, and when the control CGI111 receives a CGI request from the Web browser 2, it performs a predetermined process and outputs the link HTML111a. When the display CGI receives a CGI request from the Web browser 2, it reads the display HTML121 as a template, performs a predetermined process, and outputs the display HTML121.
As shown in Fig. 2, the link HTML111a does not have a <body> tag, and a script that automatically jumps to the CGI112 displayed in JavaScript is written in the <head> tag.
In the display HTML121, <% FORM: POWER%>, which is replaced with the processing result by the display CGI112, is written as the source code as shown in Fig. 3. In addition, the send button corresponding to the On button and Off button in FIG. 8 and the link to jump to the control CGI111 by pressing the button are written as source code.
Web browser 2 is a browser that makes a CGI request to the control CGI 111 and the display CGI 112, and can execute JavaScript.
Next, the operation of the first embodiment will be described.
FIG. 4 is a flowchart showing the operation of the first embodiment. In this figure, it is assumed that the screen for making a CGI request has already been displayed on the Web browser, and that the screen is based on the display CGI. It may also be HTML that sends FORM information to the control CGI.
First, Web browser 2 makes a CGI request to the control CGI111 with the GET method using the following script (S201).
Location.href = html.cgi / sample3.cgi? POWER = On
The control CGI111 that received the CGI request acquires the POWER value On from the FORM information (S202, CGI processing step), turns on the computer according to the acquired value (S203, CGI processing step), and outputs the link HTML111a. (S204, source code generation step, address change step).
Web browser 2 makes a CGI request to the display CGI112 by the script written in the link HTML111a (S205), and the display CGI112 that received the CGI request reads the display HTML121 as a template and controls <% FORM: POWER%>. It is replaced with the result and output to the Web browser 2 (S206, output step), and the Web browser 2 displays the display HTML121 in which the processing result is written (S207). At that time, <% FORM: POWER%> is replaced with "On", which is the power state of the computer. In addition, in the Web-UI with display HTML121, the POWER value is sent to the control CGI111 by pressing the send button.
As described above, in the first embodiment, the link HTML111a in which the link to the display CGI112 is written is output to the control CGI111, so that the web browser 2 jumps to the display CGI112 when the CGI request is made. It is no longer necessary to send the same information as the CGI request to the control CGI111 to be held to the control CGI111, and recontrol by updating can be prevented. Also, when the send button of the display HTML121 output by the display CGI112 is pressed, a CGI request is issued to the control CGI111 and the process is executed normally. Also, instead of the display CGI112, you may jump to a predetermined HTML file prepared in advance.
Embodiment 2. In the first embodiment, the link HTML and the display HTML are prepared separately, but in the second embodiment, the functions of the link HTML and the display HTML are executed by one template, and each function is controlled by a flag to be updated. Prevent recontrol.
First, the configuration of the present embodiment will be described.
FIG. 5 is a block diagram showing the overall configuration of the second embodiment, and FIG. 6 is a diagram showing the source code of the template HTML. In the second embodiment, the power supply of the computer is controlled by the Web-UI as shown in FIG. 8 as in the first embodiment.
As shown in FIG. 5, the Web server 1 has a CGI directory 11 and an HTML directory 12, and the CGI directory 11 has a control CGI113 (CGI processing unit, address change unit, source code generation unit) and a display CGI114 (output unit, source code). The rewriting part) is saved, and the template HTML122 is saved in the HTML directory 12.
Control CGI113 acquires FORM information (flags, control information) for CGI requests, performs predetermined processing according to CGI requests, reads template HTML122, acquires computer power status (status information), and acquires FORM information and status. Rewrite and output the template HTML122 according to the information. In addition, the display CGI114 acquires FORM information (flag) and status information in response to the CGI request, and rewrites and outputs the template HTML122 according to the acquired FORM information and status information.
As shown in Fig. 6, the template HTML122 has its flag determined by the JavaScript written in the <head> tag. If the flag value is 1 (DIAFLAG = 1), Web browser 2 jumps to the display CGI114 and sets the flag value to 0. When the value of the flag is 0 (DIAFLAG = 0), Web browser 2 does not jump to the display CGI114 because JavaScript is not executed, and displays the <body> tag and below.
The Web browser 2 is a browser that makes a CGI request to the control CGI 113 and the display CGI 114, and is a Web browser that can execute JavaScript.
Next, the operation of the second embodiment will be described.
FIG. 7 is a flowchart showing the operation of the second embodiment. In this figure, it is assumed that the screen for making a CGI request has already been displayed on the Web browser, and that the screen is based on the display CGI. It may also be HTML that sends FORM information to the control CGI.
First, Web browser 2 makes a CGI request to the control CGI113 with the GET method using the following script (S301).
Location.href = html.cgi / sample5.cgi? DIAFLAG = 1 & POWER = On
The control CGI113 that received the CGI request acquires the DIAFLAG value 1 and the POWER value On from the FORM information (S302, CGI processing step), and turns on the computer according to the acquired values (S303, CGI processing). Step), read the template HTML122 from the HTML directory 12, replace <% FORM: DIAFLAG%> in the template HTML122 with 1 and replace <% FORM: POWER%> with On according to the obtained FORM information, and the result. Is output to Web browser 2 (S304, source code generation step, address change step).
In the HTML output from the control CGI113, the JavaScript flag written in the <head> tag is "1" (first identifier), so the Web browser 2 makes a CGI request to the display CGI114 (S305). Also, when making a CGI request, pass DIAFLAG = 0 to the display CGI with the GET method.
The display CGI114, which has acquired the flag value 0 (second identifier) by the CGI request, further acquires the status information On indicating the power status of the computer from the Web server (S306), and reads the template HTML122 <% FORM. Replace: DIAFLAG%> with "0", replace <% FORM: POWER%> with "On", and output the result to Web browser 2 (S307, source code rewriting step, output step).
In the HTML output from the control CGI113, the JavaScript flag written in the <head> tag is "0", so Web browser 2 skips the CGI request to the display CGI114 and displays the content in the <body> tag. Display (S308). At that time, <% FORM: POWER%> is replaced with "On", which is the power state of the computer. Also, in the Web-UI with display HTML, the POWER value and flag "1" are sent to the control CGI113 by pressing the send button.
As described above, in the second embodiment, the Web browser 2 determines the flag by JavaScript, jumps to the display CGI114 when the flag of the template HTML122 is 1, and skips the JavaScript processing when the flag is 0. Then, by displaying the template HTML122 under the <body> tag, it is possible to prevent re-control by updating just by preparing one template.
Further, a program for executing each of the above-mentioned steps in a computer constituting the display control device can be provided as a display control program. The above-mentioned program can be executed by a computer constituting the display control device by storing it in a recording medium that can be read by a computer. Here, as the recording medium that can be read by the computer, an internal storage device such as ROM or RAM internally mounted on the computer, a portable storage such as a CD-ROM, a flexible disk, a DVD disk, a magneto-optical disk, or an IC card. It includes a medium, a database that holds a computer program, another computer, the database, and a transmission medium on a line.
(Appendix 1) A CGI processing unit that receives a CGI request from a client, performs CGI processing, and outputs the CGI processing result. Based on the CGI request, an address change unit that connects to a link address different from the address that the client connected to make the CGI request, and An output unit that outputs display information for displaying predetermined information based on the CGI processing result output by the CGI processing unit to the client whose connection destination has been changed by the address changing unit. Display control device equipped with. (Appendix 2) In the display control device described in Appendix 1, The address changing unit includes a source code generation unit that generates a source code for connecting the client to the link address different from the address that the client connected to make the CGI request and transmits the source code to the client. A display control device characterized by. (Appendix 3) In the display control device described in Appendix 2, The source code generator includes a predetermined information based on the CGI processing result, and is a first identifier for connecting the client to the link address different from the address to which the client was connected to make the CGI request. Generate source code including The output unit includes a source code rewriting unit that rewrites the first identifier to a second identifier and displays the predetermined information on the client to the client connected by executing the source code. A display control device characterized by. (Appendix 4) In the display control device described in Appendix 3, The first identifier is a display control device that further causes the client to skip the display processing of the predetermined information. (Appendix 5) In the display control device described in any of Appendix 1 to Appendix 4, The client is a display control device characterized by being a Web browser capable of executing an interpreted language. (Appendix 6) In the display control device described in any of Appendix 1 to Appendix 5, A display control device characterized in that the address changing unit is HTML data. (Appendix 7) In the display control device described in any of Appendix 3 to Appendix 6, A display control device, wherein the first identifier and the second identifier are discriminated by the interpreter language. (Appendix 8) A CGI processing step that receives a CGI request from a client, performs CGI processing, and outputs the CGI processing result. Based on the CGI request, an address change step of connecting the client to a link address different from the address connected to make the CGI request, and An output step that outputs display information for displaying predetermined information based on the CGI processing result output in the CGI processing step to the client whose connection destination has been changed by the address change step. A display control program that causes a computer to execute. (Appendix 9) In the display control program described in Appendix 8, The address change step includes a source code generation step of generating a source code for connecting the client to the link address different from the address connected by the client for making the CGI request and transmitting the source code to the client. A display control program characterized by. (Appendix 10) In the display control program described in Appendix 9, The source code generation step includes a predetermined information based on the CGI processing result, and is a first identifier for connecting the client to the link address different from the address to which the client was connected to make the CGI request. Generate source code including The output step includes a source code rewriting step in which the first identifier is rewritten to the second identifier and the predetermined information is displayed on the client to the client connected by executing the source code. A display control program characterized by. (Appendix 11) In the display control program described in Appendix 10, The first identifier is a display control program characterized in that the client further skips the display processing of the predetermined information. (Appendix 12) In the display control program described in any of Appendix 8 to Appendix 11, The client is a display control program characterized in that the client is a Web browser that can execute an interpreted language. (Appendix 13) In the display control program described in any of Appendix 8 to Appendix 12, The address change step is a display control program characterized in that a computer is executed by HTML data. (Appendix 14) In the display control program described in any of Appendix 10 to Appendix 13, A display control program characterized in that the first identifier and the second identifier are discriminated by the interpreter language. (Appendix 15) A CGI processing step that receives a CGI request from a client, performs CGI processing, and outputs the CGI processing result. Based on the CGI request, an address change step of connecting the client to a link address different from the address connected to make the CGI request, and An output step that outputs display information for displaying predetermined information based on the CGI processing result output in the CGI processing step to the client whose connection destination has been changed by the address change step. Display control method including. (Appendix 16) In the display control method described in Appendix 15, The address change step includes a source code generation step of generating a source code for connecting the client to the link address different from the address connected by the client for making the CGI request and transmitting the source code to the client. A display control method characterized by. (Appendix 17) In the display control method described in Appendix 16, The source code generation step includes a predetermined information based on the CGI processing result, and is a first identifier for connecting the client to the link address different from the address to which the client was connected to make the CGI request. Generate source code including The output step includes a source code rewriting step in which the first identifier is rewritten to the second identifier and the predetermined information is displayed on the client to the client connected by executing the source code. A display control method characterized by. (Appendix 18) In the display control method described in Appendix 17, The first identifier is a display control method, further comprising skipping the display processing of the predetermined information in the client. (Appendix 19) In the display control method described in any of Appendix 15 to Appendix 18, A display control method characterized in that the client is a Web browser capable of executing an interpreted language. (Appendix 20) In the display control method described in any of Appendix 15 to Appendix 19, The address change step is a display control method characterized in that a computer is executed by HTML data.
<figref num="1">It is a block diagram which shows the whole structure of Embodiment 1. FIG.</figref><figref num="2">It is a figure which shows the source code of the link HTML.</figref><figref num="3">It is a figure which shows the source code of the display HTML.</figref><figref num="4">It is a flowchart which shows the operation of Embodiment 1.</figref><figref num="5">It is a block diagram which shows the whole structure of Embodiment 2.</figref><figref num="6">It is a figure which shows the source code of the template HTML.</figref><figref num="7">It is a flowchart which shows the operation of Embodiment 2.</figref><figref num="8">It is a figure which shows the screen of the Web browser which controls the power on / off of a computer.</figref><figref num="9">This is a flow showing a malfunction due to careless update of the user in computer control by a Web browser.</figref>
Code description
1 Web server, 2 Web browser, 11 CGI directory, 12 HTML directory, 111,113 control CGI, 111a link HTML, 112,114 display CGI, 121 display HTML, 122 template HTML.
9 sheets
Sheet 1 Sheet 2 Sheet 3 Sheet 4 Sheet 5 Sheet 6 Sheet 7 Sheet 8 Sheet 9
Every citation, both waysCites: the store holds 5 of 6
| Document | Relation | Office |
|---|---|---|
| JP2002132810A | Cites | Japan |
| JP11096095A | Cites | Japan |
| JP2002507308A | Cites | Japan |
| JP09265456A | Cites | Japan |
| JP2002183085A | Cites | Japan |
| Claus Brabrand, Anders Moller, Anders Sandholm,A Runtime System for Interactive Web Services,1999年 3月 1日,[平成23年12月14日検索],URL,http://www.brics.dk/bigwig/runwig/runtime.pdf | Non-patent | – |
| シュミット クリストファー Christopher Schmitt,CSSクックブック -Webデザインのための活用テクニック集 初版 CSS Cookbook<SP>TM</SP>,株式会社オライリー・ジャパン オライリー ティム,1999年 3月29日,第1版,「本書に寄せて」及び137~138ページ | Non-patent | – |
| Romain Guay,Java Tip 136: Protect Web application control flow,Java World,2003年 3月14日,URL,http://www.javaworld.com/javaworld/javatips/jw-javatip136.html | Non-patent | – |
9 members in 5 offices
Priority claims2
| Document | Office | Kind | Date |
|---|---|---|---|
| 2007170489 | Japan | A | |
| JP20070170489 | – | – | – |
Members9
| Document | Office | Kind | |
|---|---|---|---|
| US2009006649A1 | United States of America | A1 | |
| CN101340311A | China | A | |
| KR20090004455A | Republic of Korea | A | |
| JP2009009376A | Japan | A | |
| EP2017750A1 | European Patent Office (EPO) | A1 | |
| US7805524B2 | United States of America | B2 | |
| KR101005979B1 | Republic of Korea | B1 | |
| CN101340311B | China | B | |
| JP5040472B2This record | Japan | B2 |
13 legal events, as the office reported them to INPADOC
Over the term
Point at a mark for the eventEvents
| Event | Code | |
|---|---|---|
| Cancellation because of no payment of annual feesLAPS | LAPS | |
| Renewal fee payment (event date is renewal date of database)FPAY | FPAY | |
| Certificate of patent or registration of utility modelJAPANESE INTERMEDIATE CODE: R150R150 | R150 | |
| First payment of annual fees (during grant procedure)JAPANESE INTERMEDIATE CODE: A61A61 | A61 | |
| Written decision to grant a patent or to grant a registration (utility model)JAPANESE INTERMEDIATE CODE: A01A01 | A01 | |
| Written decision to grant a patent or to grant a registration (utility model)JAPANESE INTERMEDIATE CODE: A01A01 | A01 | |
| Decision of grant or rejection writtenTRDD | TRDD | |
| Written amendmentJAPANESE INTERMEDIATE CODE: A523A521 | A521 | |
| Notification of reasons for refusalJAPANESE INTERMEDIATE CODE: A131A131 | A131 | |
| Report on retrievalJAPANESE INTERMEDIATE CODE: A971007A977 | A977 | |
| Written amendmentJAPANESE INTERMEDIATE CODE: A821A521 | A521 | |
| Written request for application examinationJAPANESE INTERMEDIATE CODE: A621A621 | A621 | |
| Notification of change in applicantJAPANESE INTERMEDIATE CODE: A711A711 | A711 |
Numbers
- Publication
- 5040472
- Publication, DOCDB
- 5040472
- Publication, EPODOC
- JP5040472B
- Application
- 170489
- Application, DOCDB
- 2007170489
- Application, EPODOC
- JP20070170489
Titles2
- Japanese
- 表示制御装置、表示制御プログラム及び方法
- English
- Display control device, display control program and method
Classification
- CPC, 6
- G06F16/972
- G06F8/30
- G06F9/265
- G06F9/45529
- G06F15/16
- G09F17/00
- IPC, 1
- G06F13 00
