JP2009065238A - Information processing apparatus - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To substitute a character string determined by one function for a plurality of tokens according to a result of processing by the one function. <P>SOLUTION: Information representing whether FAX transmission is performed normally is substituted in a return value *OUT[0] by a function sendFax and it is returned to an image processing control unit through an image processing unit. According to a query character string, the image processing control unit supplies a path of a template file OK.html to a GET processing control unit to generate an OK.htm file when *OUT[0]="OK", and supplies a path of a template file NG.html to the GET processing control unit to generate an NG.htm file when *OUT[0]="NG". A message token $msg1$ is included in the template file OK.htm and message tokens $msg1$ and $msg2$ are included in the template file NG.htm. Those are replaced with *OUT[1] and *OUT[2] through processes of steps S39 and S34 by an HTML translator 355. <P>COPYRIGHT: (C)2009,JPO&INPIT

Description

  The present invention relates to an information processing apparatus having a Web server function that enables remote operation from a Web client.

Japanese Patent Application Laid-Open No. 2004-259561 discloses that in this type of image forming apparatus, an HTML file is dynamically created by replacing each ID of an HTML template in which ID information is described with corresponding information. .
JP 2006-155356 A

  However, since it is a simple replacement, only one can be replaced with one function, and each of a plurality of tokens cannot be replaced with a corresponding character string according to the result processed with one function. For example, when FAX transmission is performed using the FAX transmission function, it is not possible to replace each of the plurality of tokens with the success or failure of the FAX transmission, the processing completion time when the transmission is successful, and the cause when the transmission fails.

  In view of such a problem, an object of the present invention is to provide an information processing apparatus capable of replacing each of a plurality of tokens with a character string determined by the function according to the result of processing by one function. It is in.

In the first aspect of the present invention,
A processor;
Storage means for storing a web application and a template file and coupled to the processor;
In the information processing apparatus including the Web application,
Functions and
In order to cause the processor to create a response body, a context token included in a specified template file, for example, a message token is substituted with a return value of the function, and the context token is The function includes an identifier, and the function has a plurality of return values corresponding to the identifier.

  In the second aspect of the information processing apparatus according to the present invention, in the first aspect, the return value is the content of the array element, and the identifier is an index for identifying the array element.

  In the third aspect of the information processing apparatus according to the present invention, in the first or second aspect, the Web application has a plurality of functions with a unified return value format, and the replacement is any of the plurality of functions. Is done independently.

  According to the configuration of the first aspect, the context token including the identifier is replaced with the return value of the function having a plurality of return values corresponding to the identifier. Each of the context tokens can be replaced with a character string determined by the function. For example, when FAX transmission is performed with the FAX transmission function, each of the plurality of context tokens is replaced with the success / failure of FAX transmission, which is a plurality of return values of this function, the processing completion time when succeeding, and the cause when failing. can do.

  According to the configuration of the second aspect, since the return value is the contents of the array element and the identifier is an index for identifying the array element, the correspondence between the context token and the plurality of return values of the function is It is simple and easy to understand.

  According to the configuration of the third aspect, since there are a plurality of functions whose return value formats are unified and the replacement is performed regardless of which of the plurality of functions, each processing of the plurality of functions is performed. There is an effect that the result can be dealt with by one template file.

  Other objects, configurations and effects of the present invention will become apparent from the following description.

  FIG. 15 is a schematic hardware block diagram of the image forming system according to Embodiment 1 of the present invention.

  The image forming apparatus 10 serving as an information processing apparatus is a multifunction machine capable of performing copying, printing, FAX transmission / reception, and electronic mail transmission. The image forming apparatus 10 also functions as a Web server machine complying with HTTP, and the image forming apparatus 10 can be remotely operated by a general-purpose browser of a host computer in the intranet.

  In the image forming apparatus 10, a PROM 13, a DRAM 14, an operation panel 15, a printer 16, a scanner 17, a NIC (Network Interface Card) 18, and a FAX modem 19 are connected to the MPU 11 through an interface 12. In FIG. 15, for simplification, a plurality of interfaces are shown as one block.

  The PROM 13 is, for example, a flash memory, and stores a general-purpose OS (operating system) having multi-process and multi-thread functions, a Web server and a Web application (including an image forming processing program), and various data described below. ing. The OS is, for example, Linux (registered trademark).

  The DRAM 14 is used for a work area, and multi-process and multi-thread instances, request messages, response messages, and data related thereto are stored and released. The operation panel 15 is used for inputting a setting value or an instruction and displaying a setting screen or a state. The printer 16 is used for image input for copying and fax transmission. The scanner 17 includes a print engine, a paper feed unit, a conveyance unit, and a paper discharge unit. The bitmap data generated in the DRAM 14 is supplied, and an electrostatic latent image is formed on the photosensitive drum based on the data. Then, this image is developed with toner, and the toner image is transferred and fixed on a sheet, and discharged. The NIC 18 is coupled to a plurality of Web client machines 20, 21,... Via a cable or a wireless communication medium. The FAX modem 19 is coupled to an arbitrary FAX apparatus 29 via the public line network 28.

  FIG. 1 is a functional block diagram mainly showing a software configuration of the image forming apparatus 10.

  In the image forming apparatus 10, an OS 30, an upper layer 31, an httpd 32, a mail transmission server 33, a main Web server 34, a Web application 35, and a DBMS (database management system) 36 are stored as programs in the PROM 13 (FIG. 15). The data includes a static resource 37, an HTML template file 38, a buffer size table 39, a language table file 40, a database 41, and a configuration file 42.

  inetd31, httpd32, and mail transmission server 33 are general-purpose programs. The characters “d” in inetd 31 and httpd 32 indicate that the daemon operates in the background, and each operates as a process. The main Web server 34, Web application 35, and DBMS 36 operate as one process.

  The reason for using inetd 31 is to simplify the configuration of the main Web server 34 by effectively using existing assets. The inetd 31 is called a super server because it monitors one or more ports described in the definition file, and is described in the definition file corresponding to the port number each time a TCP connection is established with the client. Start the program that is running. In this embodiment, inetd 31 monitors only port 80 and starts httpd 32 each time a TCP connection is established with the client. The inetd 31 also includes a security function (filter). In this embodiment, the inetd 31 accepts only a connection request from a client having a local IP address described in the definition file.

  The reason for using httpd32 is that if this is not used, the main Web server 34 is started each time the inetd 31 accepts a connection request. If the main Web server 34 is started once when the system is started, as will be described later, a thread is generated for each request in the main Web server 34 so that parallel processing is possible, and a process is generated for each request. You can save memory than you do.

  According to the first embodiment, it is possible to simplify the configuration of the memory resource saving main Web server by effectively using existing assets and shorten the development period.

  When httpd32 is activated, it receives a request message from a client whose TCP connection has been established by inetd31 from the Web client machine 20 via the NIC 18 and OS 30, passes it to the main Web server 34 through a pipe, and then disappears from the DRAM 14. . That is, httpd32 functions only as an intermediary. For this reason, only the functions necessary for this mediation are compiled and used, thereby achieving an effect of further saving the memory.

  In the main Web server 34, the HTTP processing thread generation unit 340 receives the request message from the httpd 32, generates an HTTP processing thread 341, passes the identifier of this message to the constructor of the HTTP processing thread 341, and starts the HTTP processing thread 341. Let

  The HTTP processing thread 341 parses this message and includes the path in the request URI included in the message and the query character string in the case of the GET method, each field name and its value, and in the case of the POST method, the variable name and its A value (in the present specification and claims, in the POST method, a value corresponding to a query character string in the case of the GET method is also referred to as a query character string) is assigned to a corresponding element of a variable of a predetermined structure Then, the process rough allocating unit 342 is called with the identifier (hereinafter referred to as S identifier) of the structure variable (hereinafter referred to as S variable) as an argument.

In the following process, the information in the request message is used via the corresponding element of the S variable, which simplifies each of the following processes. The element of the S variable in which the path in the request URI is stored is the S variable. The element of the S variable in which the path and query string are stored is the S variable. FIG. 3, which is referred to as a query character string, is a flowchart showing processing by the processing rough distribution unit 342. Hereinafter, the parentheses are identification codes in the figure.

  (S0) S variable. Read the path.

  (S1) If the extension of the file name included in this path is “cgi”, the process proceeds to step S2, and if not, the process proceeds to step S3.

  (S2) The Web application 35 is called with the S identifier as an argument, and the processing of FIG.

  (S3) If the path read in step S0 matches the file name described in the force file item in the configuration file 42 or is less than or equal to the directory path, the process proceeds to step S2. If not, the process proceeds to step S4. That is, if the path indicating the request target is a predetermined path, it is regarded as a request for get.cgi described later in the CGI program.

  (S4) The static resource processing unit 343 is called with the S identifier as an argument.

  In response, the static resource processing unit 343 responds to the S variable. The contents of the file identified by the path are read from the static resource 37 onto the DRAM 14, and the identifier is delivered to the corresponding HTTP processing thread 341. In response to this, the HTTP processing thread 341 adds a response header to the contents of this file and transmits this message to the Web client machine 20 via the OS 30 and the NIC 18 as a response message.

  According to the first embodiment, in the processing rough distribution unit 342, the path included in the request URI from the client matches the virtual file path described in the force file item in the configuration file 42, or less than the virtual directory path. If it is determined, the control is transferred to the Web application 35. Therefore, the program file path for transferring control to the Web application 35 can be omitted, and the description of 37 and 38 can be simplified. Play.

  Next, a process when the web application 35 is called by the process rough distribution unit 342 will be described. FIG. 2 is a functional block diagram mainly showing the configuration of the Web application 35.

  This call is made to the processing subdivision unit 350 of the Web application 35. FIG. 4 is a flowchart showing the processing by the processing fine distribution unit 350.

  Conventionally, each of the CGI programs is started as a process. However, in the first embodiment, each CGI program is started as a function (subroutine) in one process, thereby causing a delay due to interprocess communication. In addition, resources are shared by a plurality of CGI programs to reduce the necessary memory size as a whole. In other words, the advantages of the CGI method are effectively used and the drawbacks are compensated.

  (S10, S11) S variable. If the file name main body included in the path (the part obtained by removing .cgi from the file name) is “login”, the authentication control unit 351 is called with the S identifier as an argument, and the process of FIG. 4 ends.

  (S12, S13) If the file name body is “get”, the GET process control unit 352 is called with the S identifier as an argument, and the process of FIG. 4 is terminated.

  (S14, S15) If the file name body is “set”, the SET process control unit 353 is called with the S identifier as an argument, and the process of FIG. 4 is terminated.

  (S16, S17) If the file name body is “image”, the image processing control unit 354 is called with the S identifier as an argument, and the processing of FIG. 4 is terminated. Proceed to S13.

  Returning to FIG. 2, the GET process control unit 352 determines whether the S variable. The HTML translator 355 is called with the path included in the query character string as an argument. For example, if the request line is GET /cgi-bin/get.cgi?htmfile=/start/start.html HTTP / 1.1, the S variable. The query character string is htmfile = / start / start.html, and this path /start/start.html is the path of the HTML template file. In response to this call, the HTML translator 355 performs the processing shown in FIG.

  Here, for each HTML template file 38, as shown in FIG. 5B, a buffer size table 39 in which the path and the number of bytes corresponding to the file size are associated with each other is created in advance. This number of bytes is, for example, the file size itself, 1.1 times the file size or 256 bytes added to the file size.

  (S20) The number of bytes corresponding to the designated template file is read from the buffer size table 39.

  (S21) A temporary storage area of this number of bytes on the DRAM 14 is acquired via the memory manager 302 of the OS 30 shown in FIG.

  (S22) The statement on the line indicated by the statement line counter SLC is read from the template file, and this counter SLC is incremented by one.

  (S23) If there is no statement to be read in step S22, the process proceeds to step S29; otherwise, the process proceeds to step S24.

  (S24) If the statement is a directive (instruction for the HTML translator 355), the processing is performed as described later.

  (S25 to S28) If the statement is a context token (hereinafter simply referred to as a token), the statement is replaced with a corresponding character string as described later, and the statement is written to the temporary storage area. Are written in the temporary storage area as they are. Next, the process returns to step S22.

  In step S25, S27 or S28, the following processing is also performed.

  (S2A, S2B) When writing to the temporary storage area, if the temporary storage area is insufficient and cannot be written, the memory manager 302 is used to temporarily store a predetermined percentage of the size acquired in step S20, for example, 10%. Increase the storage area.

  FIG. 6 is a flowchart showing details of step S27 in FIG.

  (S30) A token body is extracted from the token. Here, the token is a character string including a token start symbol # and a token end symbol #, such as # l_NetworkSetting # or # f_GetIPAddress #. A character string between # and # in the token is called a token body. The first part of the token body indicates the type of token. When the first two characters are l_ and f_, it indicates a language token and a function token, respectively. When the first three characters are msg, Indicates a token.

  (S31) If the first two characters of the token body are l_, the process proceeds to step S32. If f_, the process proceeds to step S36, and if the first three characters are msg, the process proceeds to step S39.

  (S32) The token name is converted into a hash value. Here, the token name is a character string after the third character in the token body in the language token.

  The language table file 40 has a language table file for each national language, and each table associates a hash value of a token name with a character string that is a value of the token name.

  (S33) Using the hash value converted in step S32 as a key, the contents of the designated language table file are searched to obtain a corresponding value. For example, if the token name is NetworkSeting, “Network Setting” is obtained if the specified language is English, and “Network Setting” is obtained if the specified language is Japanese.

  The designated language is initially a default value, and is changed as described later, held in a lang cookie, and one in the language table file 40 is designated by the lang value. For example, lang = 0 indicates English and lang = 2 indicates Japanese.

  (S34) The token is converted with the value. For example, when lang = 0 and the language token is # l_NetworkSetting #, this token is converted to “Network Setting”.

  Here, the format of the argument and return value of each function in the processing function group 356 is unified, and an arbitrary function func is expressed as func (chr ** IN, chr *** OUT) in C language. . Both the argument IN and the return value OUT are one-dimensional dynamic arrays of character strings. The reason that one more symbol * is added to OUT than to IN is to allow the function side to change the number of array elements in the return value OUT, that is, it can be a dynamic array on the function side. It is for doing so.

  In the case of a function token, this is converted to the return value * OUT [0] of the function with that function name. In the case of message token # msgX # (X is a natural number), this is converted to the return value * OUT [X] of the function.

  (S35) A token can be included in the token value. If this value includes a token, the process returns to step S30; otherwise, the process of FIG. 6 ends.

  (S36, S37) If an argument is included in the function token, the argument is extracted.

  The argument is described in the same format as the query string, and multiple arguments can be included in the function token by & as a delimiter. The third and subsequent characters of the token body in a function token up to & (or the end if &) is called the function name. For example, the function token # f_func & arg1 = XXX & arg2 = YYY & arg3 = ZZZ # indicates that the function name is func, the argument name arg1 is XXX, the argument name arg2 is YYY, and the argument name arg3 is ZZZ. In general, the value of the argument name argX is assigned to the argument IN [X].

  (S38) An argument included in the function token is passed to the function having the function name included in the function token, and this function is called. Next, the process proceeds to step S34.

  This function is included in the processing function group 356 of FIG. The function can read or change data in the database 41 via the DBMS 36. This data includes various setting values of the image forming apparatus, the remaining amount of toner, the number of printed sheets, and the like.

  (S39) The index X (X ≧ 0) is extracted from the message token # msgX #, and the process proceeds to step S34.

  For example, the function getDHCPMode identified by the function token # f_getDHCPMode # returns * OUT [0] = “# l_dhcp_on #”, # f_getDHCPMode # is replaced with # l_dhcp_on # in step S34, and the process returns from step S35 to step S30. If lang = 0, "DHCP ON" is obtained in step S33, # l_dhcp_on # is replaced with "DHCP ON" in step S34, and if lang = 2, "DHCP on" is obtained in step S33. In S34, # l_dhcp_on # is replaced with “DHCP on”.

  Therefore, the token can be appropriately converted according to both the variable and the language.

  As another example, when lang = 2, the language token # l_jobnum_msg # is converted to "# f_getJobNum # jobs currently being processed." And the function token # f_getJobNum # is * OUT [0] = " As a result, the language token l_jobnum_msg # is converted to "10 jobs currently being processed." If lang = 0, the language token # l_jobnum_msg # is converted to "# f_getJobNum # jobs are being processed", and the function token # f_getJobNum # is converted to * OUT [0] = "10", resulting in the language The token l_jobnum_msg # is converted to "10 jobs are being processed".

  Therefore, even if the position of the variable value “10” in the sentence is different between English and Japanese, it is possible to cope with it.

  According to the first embodiment, since the format of the return values of a plurality of functions included in the Web application 35 is unified, the entire configuration of the Web application can be simplified and software design by the team can be easily performed. This has the effect of contributing to shortening the development period of products whose functions have been expanded or changed.

  In addition, since each of a plurality of functions can have a plurality of return values on the function side, the information obtained by executing one function can be used for different purposes at a plurality of locations, and a complicated configuration can be simplified. There is an effect that can be made.

  The DBMS 36 mainly imposes a restriction on the change of the setting value, and restricts the range of the value or at the same time restricts the number of clients that can change the setting value to one person.

  FIGS. 14A and 14B are sequence diagrams showing an outline of message transmission / reception between the Web client machine 20 and the image forming apparatus 10.

  In FIG. 14A, the top page of the site of the image forming apparatus 10 is requested from the browser of the Web client machine 20, and the image forming apparatus 10 responds to this by, for example, displaying the top page of the Web client machine 20 on the browser of FIG. A screen as shown in (A) is displayed. The HTML file on this screen has a language selection form and a form for instructing movement to a print screen or FAX transmission screen.

  In this language selection form, when the user selects an item (language) in the pull-down menu and presses the Go button, a request message including information on the selected language is transmitted to the image forming apparatus 10, and in FIG. Processing moves from the distribution unit 350 to the GET processing control unit 352, and then the HTML translator 355 converts the language token included in the template file on the top page into a character string of the selected language, which is then transferred to the GET processing control unit 352. returned. The GET processing control unit 352 adds a cookie field of the selected language to this response body, adds the remaining response header via the HTTP processing thread 341, and completes the request message. The HTTP processing thread 341 transmits this response message to the Web client machine 20 via the OS 30 and the NIC 18. As a result, the content shown in FIG. 9A is displayed in the selected language on the browser of the Web client machine 20. The HTTP processing thread 341 disappears after this transmission.

  In subsequent request messages transmitted from the Web client machine 20 to the image forming apparatus 10, a cookie indicating the selected language is included in the request header, so that the language of the character string displayed on the browser is selected. Become.

  In the screen movement form, when the user selects a radio button on the FAX transmission screen and presses the movement button, a request message including get.cgi in the request URI is transmitted to the image forming apparatus 10, and image formation is performed in the same manner as described above. A response message is generated by the device 10 and transmitted to the Web client machine 20, and a screen as shown in FIG. 9B is displayed on the browser.

  The user selects a FAX transmission destination from the pull-down menu, and then clicks the browse button to display a file selection dialog for the browser, selects a file stored on the hard disk of the Web client machine 20 and selects a transmission file. When specified and the FAX transmission button is pressed, a request message including the selected destination and the content of the transmission file is transmitted to the image forming apparatus 10.

  The request line included in this request message is, for example, POST / cgi-bin / image.cgi HTTP / 1.1, and the file name is image.cgi, so the processing sub-distribution unit 350 to the image processing control unit in FIG. Control transfers to 354. The query character string included in the request body of this message is, for example, func = sendFax & arg0 = sendfile.pdf & arg1 = 1 & okhtmfile = OK.html & failhtmfile = NG.html, which is the above S variable. Stored in the query string. The image processing control unit 354 passes the S identifier to the image processing unit 357, and based on this, the image processing unit 357 processes IN [0] = "sendfile.pdf", IN [1] = "1" as arguments. The function sendFax in the function group 356 is called. In the function sendFax, the setting value used for FAX transmission is acquired from the database 41 or from a cookie described later, via the setting value acquisition function in the processing function group 356. This also applies to image processing other than FAX transmission. The function sendFax converts the content of the transmission file sendfile.pdf into image data for FAX transmission using the acquired setting value, and transmits the FAX to the first destination in the address book.

  Information indicating whether or not the transmission has been normally performed is substituted into a return value * OUT [0] in the function sendFax, and this is returned to the image processing control unit 354 via the image processing unit 357. Based on the query character string, the image processing control unit 354 gives the path of the template file OK.html to the GET processing control unit 352 to generate an OK.htm file if * OUT [0] = "OK". If * OUT [0] = "NG", the path of the template file NG.html is given to the GET processing control unit 352 to generate the NG.htm file. In the present embodiment, the extension of the template file is html, and the extension of the file created based on this is htm.

  For example, as shown in FIG. 11A, the template file OK.html includes a message token # msg1 #, and as shown in FIG. 11C, the template file NG.html has a message token # msg1 # and # msg2 # is included, and message tokens # msg1 # and # msg2 # are replaced with * OUT [1] and * OUT [2], respectively, by the processing of steps S39 and S34 in FIG. 6 by the HTML translator 355. The Thereby, HTML files OK.htm and NG.htm as shown in FIGS. 11B and 11D are generated by the GET processing control unit 352 from the template files OK.html and NG.html, respectively. In either case, a response header is added to the request via the GET processing control unit 352 and the HTTP processing thread 341 and transmitted to the Web client machine 20.

  The GET processing control unit 352 also creates an e-mail with the contents of the HTML file OK.htm or NG.htm to notify the user of transmission completion or transmission failure according to the setting, and sends the e-mail of the mail transmission server 33. It is stored in a box (see FIG. 10).

  According to the first embodiment, since the format of the return value of each function in the processing function group 356 is unified as described above, based on the same template file OK.html and NG.html, other than the FAX transmission result A response message body indicating an image processing result or a set value change result can also be created, which simplifies the configuration.

  Even if different template files are used for each type of processing, the return value of the function and the message token are associated with each other in a unified manner. For example, as shown in FIG. There is an effect that a file can be easily created. FIG. 11F shows an HTML file OK.htm created based on the template file OK.html shown in FIG.

  Returning to FIG. 9B, the number of destinations included in the pull-down menu changes as the user adds or deletes it using the screen shown in FIG. Corresponding to such a change, a template file as shown in FIG. This template file includes a for directive <!-For f_getCountOfAddress-> and an end_for directive <!-End_for->. A directive is identified by its start symbol <!-And end symbol->.

  The processing for the statement arranged between the for directive and the end_for directive is repeated by the number of repetitions f_getCountOfAddress included in the for directive. The number of repetitions may be a constant, but in this example, a function token f_getCountOfAddress in which the token identification symbol # is omitted is used as a variable. The function getCountOfAddress identified by this function token obtains the number of destinations included in the address book, and the function token is replaced with the return value * OUT [0].

  F_m_ in the token “# f_m_Count & arg0 = 0 #” included in the option tag indicates that the function Count is a multivalent function. This function is the same as the above-mentioned function in which the argument and return value formats are unified, but the function is handled differently depending on the value of the internal counter i indicating the number of repetitions in the for directive. This function is called only when the counter i is the initial value 0 (first repetition), and the multi-function token “# f_m_Count & arg0 = 0 #” is replaced with * OUT [i] for each i for i ≧ 0. The same applies to the multivalent function token # f_m_getAddress # that substitutes the i-th destination in the address book for * OUT [i].

  The directive is processed in step S25 in FIG. FIG. 7 is a flowchart showing details of processing mainly for the for directive in step S25.

  (S40) If it is a for directive (for DIR), the process proceeds to step S41; otherwise, the process proceeds to step S4C.

  (S41) The initial value 0 is assigned to the repetition counter i, and the value of the row counter SLC indicating the number of rows in the template file of the processing target statement is assigned to SLC0 and saved.

  (S42) The statement of the line indicated by the counter SLC is read from the template file, and this line counter is incremented by one.

  (S43) If a multivalent function token is included in this statement, the process proceeds to step S44, and if not, the process proceeds to step S47.

  (S44, S45) Only when i = 0, the function identified by the multivalent function token in the processing function group 356 is called. At this time, if the multivalent function token includes an argument, it is extracted and delivered to this function. For example, when the multivalent function token is “# f_m_Count & arg0 = 0 #”, IN [0] = “0” is delivered and the function Count is called. The function * OUT [i] is obtained by converting in [0] into a numerical value and adding the value i to a character type.

  (S46) The multivalent function token is replaced with * OUT [i], and the process proceeds to step S48.

  (S47) Perform processing according to the statement.

  (S48) If it is an end_for directive, the process proceeds to step S49; otherwise, the process returns to step S42.

  (S49) The repeat counter i is incremented by 1.

  (S4A) If the value of i is equal to the value imax specified in the for directive, the process of FIG. 7 is terminated, otherwise the process proceeds to step S4B.

  (S4B) SLC0 is assigned to the statement line counter SLC, and the process returns to step S42.

  (S4C) Processing for other directives is performed, and the processing of FIG. 7 ends.

  The HTML file as shown in FIG. 12B is generated as a response body by the HTML translator 355 based on the template file shown in FIG. .

  Comparing FIG. 12A and FIG. 12B, it is clear that a pull-down menu having an arbitrary number of items can be created with a simplified template file. The for directive is also applicable to control loops such as other while statements and do-loops used in command statements such as C language.

  Next, as a specific example of the SET process, a process for adding, changing, or deleting an item (destination) in the address book will be described.

  In FIG. 14B, after moving from the screen of FIG. 9A to the screen of FIG. 9B, the “Open Address Book” button is clicked to move to the screen of FIG. To show when this is successful.

  The response message corresponding to the request message obtained by clicking the “open address book” button is the same as the response message corresponding to the request message obtained by clicking the “move” button in FIG. Created. The response body of this message is generated by the HTML translator 355 based on the template file shown in FIG. 13A, and is shown in FIG. 13B, for example. The for directive and the multivalent function token in FIG. 13A are the same as those in FIG.

  In FIG. 9C, when an item in the list box is clicked and selected, this item is highlighted and the client side on-click event handler is called to display the selected item in the destination box. Is done. When the user selects the “Delete” radio button in this state, or changes the character string in the destination box and selects the “Change” radio button and presses the execute button, the data in the destination box A request message including the selected data indicating “change” or “deletion” and the attribute value of the FORM tag shown in FIG. 13B is transmitted to the image forming apparatus 10.

  In the image forming apparatus 10, the SET processing control unit 353 is activated with the above S identifier corresponding to this message as an argument, and the address book data in the database 41 is updated via the corresponding function in the processing function group 356 and the DBMS 36. Or deleted.

  Also, when the user enters the destination to be added in the destination box of FIG. 9C, selects the “Add” radio button and presses the execution button, this destination and addition are indicated as described above. A request message including the data and the attribute value of the FORM tag shown in FIG. 13B is transmitted to the image forming apparatus 10, and the address book data in the database 41 is set via the SET processing control unit 353, the processing function group 356, and the DBMS 36. This destination is added.

  As another example of setting value change, when the FAX transmission setting value button is pressed on the screen shown in FIG. 9B, a response message for displaying the screen shown in FIG. 10 is displayed in response to the request message. The image is transmitted from the image forming apparatus 10 to the Web client machine 20. This screen displays a call count selection drop-down list until FAX reception, a transmission completion / failure notification means selection drop-down list, a destination thereof, and an address book selection drop-down list. The notification means selection drop-down list includes items “e-mail”, “mobile phone”, and “none”.

  Here, in the database 41 of FIG. 2, the client ID and the destination address for each notification means are registered, and when the destination is “registered destination” in FIG. Is used. The address book selected in FIG. 10 is used in FIGS. 9B and 9C.

  Types of setting value change include my setting and common setting. My settings are settings for each client, and common settings are settings common to each client.

  My setting is for rewriting a setting value for each user by a cookie without changing the common setting for a part or all of the common setting. The value of this cookie is used in a setting value acquisition function in the processing function group 356. That is, this function obtains the corresponding setting value (common setting value) in the database 41 via the DBMS 36 if there is a corresponding one in the cookie.

  The common setting is a setting stored in the database 41, and is used as a setting value of an item that cannot be rewritten by a cookie. That is, the setting value acquisition function in the processing function group 356 acquires the common setting value in the database 41 for items that are not individually changed by the cookie in My Settings.

  “Common” shown in FIG. 10 indicates that the value of the common setting is used in My Settings (cookie is not used) or is not changed in the common settings. Changing common setting values is allowed only when logged in with administrator privileges. Whether or not the user is logged in with administrator authority is determined by an authentication cookie described later.

  When logged in with administrator authority, the setting value acquisition function in the processing function group 356 acquires the common setting value in the database 41.

  When the “change” button is pressed, a request message including the information shown in FIG. 10 is transmitted to the image forming apparatus 10, and the processing shown in FIG. 8 is performed in the SET processing control unit 353 in FIG. Done.

  (S50) Based on the S variable, the SET processing control unit 353, for example, IN [0] = "my" ("My setting"), IN [1] = "common" (the number of calls until FAX reception is "common" )), IN [2] = "e-mail" (notification means is "e-mail"), IN [3] = "same" (address is "registration destination"), IN [4] = "DesignDepartment" ( The address book is “DesignDepartment”) and the FAX transmission setting value change function is called.

  (S51) The FAX transmission setting value change function determines whether common setting or my setting is selected based on IN [0]. If it is determined to be the former, the process proceeds to step S52, and if it is determined to be the latter Then, the process proceeds to step S57.

  (S52) Based on the authentication cookie, the FAX transmission setting value change function determines whether or not the user is logged in with administrator authority. If the determination is affirmative, the process proceeds to step S53. Otherwise, the process proceeds to step S56. .

  (S53) The FAX transmission setting value change function updates the corresponding setting value stored in the database 41 via the DBMS 36 with the values of IN [1] to IN [4]. However, if IN [1] = "common", the number of calls until FAX reception is not updated. If IN [3] = "same", the notification destination is not updated.

  (S54) The FAX transmission set value change function assigns “OK” to * OUT [0] when the DBMS 36 permits change of the set value for IN [3], and * OUT [0] when it is prohibited. "NG" is assigned to, and a character string indicating the cause is obtained from the DBMS 36 and assigned to * OUT [1]. From the set value change function, the process returns to the SET process control unit 353.

  (S55) If * OUT [0] is “OK”, “NG”, or “NotAuth”, the SET processing control unit 353 takes the path of the template file OK.html, NG.html, or NotAuth.html as an argument, respectively. Call the GET processing control unit 352.

  In response to this, the GET processing control unit 352 creates an HTML file based on the template file via the HTML translator 355, and adds a part of the response header to this file. In the created NotAuth.htm, an input box for the user ID and password is described in the form. The GET processing control unit 352 adds the remaining response header via the HTTP processing thread 341, transmits it to the Web client machine 20 as a response message, and ends the processing of FIG.

  The user ID and password may be entered on the top page of the image forming apparatus 10 site.

  (S56) “NotAuth” is substituted into * OUT [0], and the process proceeds to step S55.

  (S57) The value of the corresponding element of the structure variable identified by the R identifier, that is, the name of the setting value in FIG. Except for cookies. This cookie is used as a header field in step S55.

  (S58) If IN [1] is not “common”, it is determined whether the number of characters satisfies the condition. If an affirmative determination is made, “OK” is assigned to * OUT [0] and a negative determination is made. In this case, "NG" is assigned to * OUT [0] and a character string indicating the cause is assigned to * OUT [1]. Next, the process proceeds to step S55.

  By such processing, it is possible to easily and easily perform the my setting and the common setting, and it is possible to provide a service according to the user.

  In addition, since the response body is generated via the GET processing control unit 352 depending on whether the processing in the SET processing control unit 353 is successful, the software configuration is simplified by effectively using the GET processing in the SET processing. There is an effect that can be done.

  The common settings can also be changed directly by operating the operation panel 15 with administrator authority.

  In step S52, it is determined that the user does not have a valid authority, and the user ID and password are input on the NotAuth.htm display screen on the browser, and data corresponding to this is transmitted to the image forming apparatus 10 as a request message. . The request line of this message is, for example, POST / cgi-bin / login.cgi HTTP / 1.1, and the authentication control unit 351 is activated in FIG. 2 with the above S identifier as an argument.

  The authentication control unit 351 calls the function Auth in the processing function group 356 with the user's data stored in the element of the S variable as an argument. This function determines whether or not the data corresponding to this data is registered in the database 41 via the DBMS 36. If an affirmative determination is made, “OK” is assigned to * OUT [0], and a negative determination is made. If this happens, substitute "NotAuth" for * OUT [0]. The authentication control unit 351 performs the same process as in the SET process according to the contents of * OUT [0]. However, when * OUT [0] = “OK”, the authentication control unit 351 responds with an authentication cookie indicating authentication and whether or not the administrator has authority, for example, Set-Cookie: login = admin_1068625073. It is added to the response body as a header field. After the Web client machine 20 receives this cookie, the cookie is included in the request message transmitted from the Web client machine 20 to the image forming apparatus 10.

  According to the first embodiment, in the Web application 35, the processing sub-distribution unit 350 controls any one of the plurality of processing control units 351 to 354 based on the file name of the path included in the request URI from the client. Since each of the plurality of processing control units 351 to 354 directly or indirectly performs processing via at least one of the processing function group 356, a new function can be added to the processing function group 356. The function can be easily expanded or changed by changing one or more functions in the processing function group 356 or adding a new processing control unit to the plurality of processing control units 351 to 354. It has a significant effect and contributes to shortening the development period of new products.

  The present invention includes various modifications in addition to the above.

  For example, although the case where CGI is used has been described in the above embodiment, since the present invention is characterized by a processing method that is not limited to CGI, a configuration using ASP, JSP, or the like may be used instead of CGI.

  The return value of the function may be a function value. The function may be a subroutine in a programming language that distinguishes a function from a subroutine, or a member function of a class. The argument may be passed to the function via a member variable.

  Furthermore, the template file is not limited to the one for creating an HTML file, and may be for creating another file such as an XML file.

  Further, the message token can be used other than the message.

  Further, in step S3 in FIG. 3, when the extension of the file name included in the path indicates a template file, the configuration may proceed to step S2. In FIG. 4, if the file name extension is not “cgi”, the process may proceed to step S13. The path of the force file item and the path compared thereto may be real paths.

  Furthermore, a configuration in which the processes of FIGS. 3 and 4 are combined into one, or a configuration in which the DBMS 36 is not used may be used. The main Web server 34, the Web application 35, and the DBMS 36 may be configured to operate as processes.

  Alternatively, the HTTP processing thread generation unit 340 may include these functions without using the general-purpose inetd 31 and httpd 32.

  Moreover, although the case where the information processing apparatus is an image forming apparatus has been described in the above embodiment, the present invention is not limited to this, and the present invention only needs to include the configuration described in the claims.

2 is a functional block diagram mainly showing a software configuration of an image forming apparatus. FIG. It is a functional block diagram which mainly shows the structure of the web application in FIG. It is a flowchart which shows the process by the process rough distribution part in FIG. It is a flowchart which shows the process by the process fine distribution part in FIG. (A) is a flowchart showing processing by the HTML translator in FIG. 2, and (B) is an explanatory diagram of a buffer size table in which the path and the number of bytes corresponding to the file size are associated with each HTML template file. is there. It is a flowchart which shows the detail of step S27 in FIG. 5 (A). It is a flowchart which shows the detail of the process with respect to a for directive mainly in step S25 in FIG. 5 (A). FIG. 11 is a flowchart showing processing in a SET processing control unit of the image forming apparatus and a part related thereto in response to pressing of a “change” button on the browser shown in FIG. (A)-(C) is a figure which respectively shows the top page screen, FAX transmission screen, and address book edit screen which are displayed on the browser of a client. It is a figure which shows the FAX transmission setting value change screen displayed on the browser of a client. (A) is an explanatory diagram of an HTML template file including a message token, which is generally used when processing is successful, and (B) is an explanatory diagram of an HTML file generated by an HTML translator based on the HTML template file. (C) is an explanatory diagram of an HTML template file including a message token, which is generally used in the case of processing failure, (D) is an explanatory diagram of an HTML file generated by an HTML translator based on this HTML template file, (E () Is an explanatory diagram of an HTML template file including a message token used when the FAX transmission processing is successful, and (F) is an explanatory diagram of an HTML file generated by an HTML translator based on the HTML template file. (A) is an explanatory diagram of an HTML template file including a multivalent function token for creating an HTML file corresponding to the screen shown in FIG. 9 (B), and (B) is an HTML translator based on the HTML template file. It is explanatory drawing of the produced | generated HTML file. (A) is an explanatory diagram of an HTML template file including a multivalent function token for creating an HTML file corresponding to the screen shown in FIG. 9 (C), and (B) is an HTML translator based on the HTML template file. It is explanatory drawing of the produced | generated HTML file. 9A is a sequence diagram showing an outline of message transmission / reception between the Web client machine and the image forming apparatus related to FIGS. 9A and 9B, and FIG. 9B is a sequence diagram of FIGS. FIG. 5 is a sequence diagram showing an outline of related message transmission / reception between a Web client machine and an image forming apparatus. 1 is a schematic hardware block diagram of an image forming system according to Embodiment 1 of the present invention.

Explanation of symbols

10 Image forming apparatus 11 MPU
12 Interface 13 PROM
14 DRAM
15 Operation panel 16 Printer 17 Scanner 18 NIC
19 FAX modem 20, 21 Web client machine 28 Public line network 29 FAX device 30 OS
300 NIC driver 301 Memory manager 31 inetd
32 httpd
33 Mail Transmission Server 34 Web Server 340 HTTP Processing Thread Generation Unit 341 HTTP Processing Thread 342 Processing Coarse Distribution Unit 343 Static Resource Processing Unit 35 Web Application 350 Processing Fine Distribution Unit 351 Authentication Control Unit 352 GET Processing Control Unit 353 SET Processing Control unit 354 Image processing control unit 355 HTML translator 356 Processing function group 357 Image processing unit 36 DBMS
37 Static resources 38 HTML template file 39 Buffer size table 40 Language template file 41 Database 42 Configuration file

Claims (6)

A processor;
Storage means for storing a web application and a template file and coupled to the processor;
In the information processing apparatus including the Web application,
Functions and
A translator that replaces the context token contained in the specified template file with the return value of the function to cause the processor to create a response body;
And the context token includes an identifier, and the function has a plurality of return values corresponding to the identifier.   The information processing apparatus according to claim 1, wherein the return value is a content of an array element, and the identifier is an index for identifying the array element. The Web application has a plurality of functions whose return value formats are unified,
The information processing apparatus according to claim 1, wherein the replacement is performed regardless of which of the plurality of functions is performed. The storage means further stores a database and has a plurality of the template files,
The web application further includes
A GET processing control unit that causes the processor to create a response message body based on a specified template file via the translator;
Based on the query character string from the client, the processor changes the setting data included in the database via the corresponding one of the plurality of functions, and is designated by the query character string, depending on the success or failure of the change A SET processing control unit that designates a fixed template file and transfers control to the GET processing control unit;
The information processing apparatus according to claim 3, wherein a context token is included in a template file that is determined according to success or failure of the change. The web application further includes
The processor processes the contents of the file included in the request message from the client, specifies the template file specified by the query character string from the client and determined according to the success / failure of the contents processing, and sends it to the GET processing control unit. An image processing control unit for transferring control;
The information processing apparatus according to claim 4, wherein a context token is included in a template file determined according to success or failure of the content processing.   6. The information processing apparatus according to claim 4, wherein the plurality of return values include a value indicating the success or failure, and further include a value indicating the cause when the success or failure indicates failure. .

Images