JP2005025476A - Device, method and program for converting data, and recording medium - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a data converting device for providing function of converting a data form via a network, and to provide its method, its program and a recording medium thereof. <P>SOLUTION: The data converting device includes a data converting means for converting the data form of a prescribed kind of data. The device comprises a communication means for receiving a request to convert the data form of the prescribed kind of data which is transmitted via the network; and a conversion request processing means for allowing the data converting means to convert the data form of the prescribed kind of data, based on the conversion request which the communication means receives. <P>COPYRIGHT: (C)2005,JPO&NCIPI

Description

[0001]
BACKGROUND OF THE INVENTION
The present invention relates to a data conversion apparatus, a data conversion method, a data conversion program, and a recording medium that execute data format conversion.
[0002]
[Prior art]
At present, data in various data formats can be seen. There are many well-known data formats, such as text format, BITMAP format, JPEG format, PDF format, and GIF format.
[0003]
In addition, application-specific formats such as word processing software and spreadsheet software are also defined. Each data format has its own characteristics, and the user uses it according to the purpose.
[0004]
If these data formats can be converted, it is convenient for the user. In response to this demand, software for converting the data format (hereinafter referred to as “conversion software”) has already been provided. The user can convert predetermined document data into data in a desired data format by using conversion software.
[0005]
[Problems to be solved by the invention]
However, the conversion software needs to be installed and used for each terminal. In today's development of network technology, it is very inefficient to install software on each terminal. That is, it is not a desirable system form from the viewpoint of resource efficiency in the entire system as well as the effort required for installation.
[0006]
Also, in today's diversified types of terminals such as mobile phones and PDAs (Personal Digital (Data) Assistants), services are provided not only from PCs (Personal Computers) but also from various terminals. It is desirable to be able to do it.
[0007]
The present invention has been made in view of the above points, and it is an object of the present invention to provide a data conversion apparatus, a data conversion method, a data conversion program, and a recording medium that can provide a data format conversion function via a network. And
[0008]
[Means for Solving the Problems]
Accordingly, in order to solve the above-described problem, the present invention provides a data conversion apparatus having a data conversion means for converting the data format of predetermined data, and converting the data format of the predetermined data transmitted via a network. Communication means for receiving a request, and conversion request processing means for causing the data conversion means to convert the data format of the predetermined data based on the conversion request received by the communication means.
[0009]
In such a data conversion apparatus, data conversion can be performed based on a data conversion request transmitted via the network, and therefore a data conversion function via the network can be provided.
[0010]
In order to solve the above problems, the present invention may be a data conversion method in the data conversion apparatus, a data conversion program for causing a computer to execute the data conversion method, and a storage medium on which the data conversion program is recorded.
[0011]
DETAILED DESCRIPTION OF THE INVENTION
Hereinafter, embodiments of the present invention will be described with reference to the drawings. FIG. 1 is a diagram showing a configuration example of a data conversion system according to an embodiment of the present invention. As shown in FIG. 1, the data conversion system 1 according to the present embodiment includes a data conversion server 10, a document management server 20, a Web server 30, a terminal 40, and the like, each of which includes the Internet, a LAN, and the like. They are connected via the network 50.
[0012]
The data conversion server 10 is a computer that provides a data format conversion function of document data (hereinafter referred to as a “data conversion function”) as a Web service.
[0013]
The document management server 20 is a computer having a document management database (document management DB) for managing document data, and provides functions such as search and update of document data as a Web service.
[0014]
The Web server 30 is a so-called Web server for providing functions such as the data management server 10 and the document management server 20 as Web pages.
[0015]
The terminal 40 is a terminal having a communication function such as a PC (Personal Computer), a PDA (Personal Digital (Data) Assistant), or a mobile phone that provides an interface for the user to use the data conversion system 1. In addition, although the terminal 40 is shown as one block in the figure, it does not mean that it is physically limited to one terminal. Like a general information system, it is possible to connect a large number of terminals.
[0016]
Next, a hardware configuration example of the data conversion server 10 will be described. FIG. 2 is a diagram illustrating a hardware configuration example of the data conversion server according to the embodiment of the present invention. The data conversion server 10 in FIG. 2 includes a drive device 100, an auxiliary storage device 102, a memory device 103, an arithmetic processing device 104, and an interface device 105 that are connected to each other via a bus B. Is done.
[0017]
A data conversion program for realizing document data conversion processing in the data conversion server 10 is provided by a storage medium 101 such as a CD-ROM. When the storage medium 101 on which the data conversion program is recorded is set in the drive device 100, the data conversion program is installed from the storage medium 101 to the auxiliary storage device 102 via the drive device 100.
[0018]
The auxiliary storage device 102 stores the installed data conversion program and also stores necessary files and data. The memory device 103 reads the data conversion program from the auxiliary storage device 102 and stores it when there is an instruction to start the data conversion program. The arithmetic processing unit 104 executes functions related to the data conversion server 10 in accordance with a data conversion program stored in the memory device 103. The interface device 105 includes, for example, a modem, a router, etc., and is used for connecting to a network.
[0019]
The document management server 20 and the Web server 30 can have the same configuration.
[0020]
Next, a functional configuration example of the data conversion system 1 will be described. FIG. 3 is a diagram illustrating a functional configuration example of the data conversion system according to the embodiment of the present invention.
[0021]
The data conversion server 10 includes a SOAP listener 11, a conversion job processing unit 12, a data conversion unit 13, an asynchronous management unit 14, a document management connection unit 15, a queue access unit 16, a job queue 17, and the like.
[0022]
The SOAP listener 11 is a module that provides a function for allowing a later-described method of the conversion job processing unit 12 to be called from a Web server 30 or the like by a SOAP (Simple Object Access Protocol) RPC (Remote Procedure Call). .
[0023]
The conversion job processing unit 12 is a module that controls the entire document data conversion process, and includes a conversion request reception method, a conversion execution method, and the like.
[0024]
The conversion request receiving method is a method for receiving a conversion request from the Web server 30 or the like by SOAP RPC, and information (hereinafter referred to as “job”) to be executed based on the received conversion request. , “Job information”) is registered in the job queue 17 using the queue access unit 16.
[0025]
The conversion execution method is a method for executing document data conversion processing based on job information registered in the job queue 17.
[0026]
The data conversion unit 13 is a module in which a document data conversion function is implemented. The document data conversion function includes conversion to PDF, text, BITMAP, JPEG, JPEG2000, PNG, TIFF, or the like. The data conversion unit 13 may use commercially available data conversion software or the like.
[0027]
The asynchronous management unit 14 is a module for periodically calling the conversion execution method of the conversion job processing unit 12 and is resident as an independent process.
[0028]
The document management connection unit 15 is a module that provides an interface for calling a function of the document management unit 22 in the document management server 20 by SOAP RPC.
[0029]
The queue access unit 16 is a function group for operating the job queue 17. The job queue 17 is for temporarily storing job information. In the present embodiment, the job queue 17 is composed of folders and files.
[0030]
The document management server 20 includes a SOAP listener 21, a document management unit 22, a document management DB 23, and the like. The SOAP listener 21 is a module in which a function for enabling the function of the document management unit 22 to be called by a SOAP RPC.
[0031]
The document management unit 22 is a module that provides an interface for operating the document management DB 23. For example, the document management unit 22 registers a document acquisition method for acquiring document data from the document management DB 23, a document list acquisition method for acquiring document data list information, and document data in the document management DB 23. It has a document registration method.
[0032]
The document management DB 23 is a database that stores document data.
[0033]
The Web server 30 includes an httpd 31, a Web application 32, a SOAP proxy 33, and the like. The httpd 31 is a daemon program that controls HTTP communication with the terminal 40. When the httpd 31 receives an HTTP request from the terminal 40, the httpd 31 calls the Web application 32 corresponding to the URL specified in the HTTP request, and transmits the Web page output as a processing result by the Web application 32 to the terminal 40.
[0034]
The web application 32 is a so-called web application whose main function is to generate a web page. The Web application 32 makes a predetermined processing request to the data conversion server 10 and the document management server 20 as required by SOAP RPC, and generates a Web page for displaying the result. For example, the Web application 32 generates a Web page (hereinafter referred to as “document list page”) that displays a list of document data managed in the document management DB 23 of the document management server 20.
[0035]
The SOAP proxy 33 is a module that provides an interface for calling the functions of the data conversion server 10 and the document management server 20 by SOAP RPC to the Web application 32. The SOAP proxy 33 enables the Web application 32 to call the method of the functions of the data conversion server 10 and the document management server 20 transparently without being aware of network communication.
[0036]
In the figure, the Web application 32 is shown as one block, but there are a plurality of instances. For example, a source code is mounted for each module for generating a document management list page and other modules for generating other Web pages.
[0037]
The terminal 40 has a web browser 41. The user can browse a web page transmitted from the web server 30 by the web browser 41 of the terminal 40.
[0038]
Hereinafter, the processing of the data conversion system 1 will be described. From the viewpoint of the synchronization of the processing (first viewpoint) between the data conversion server 10 and the client side (Web server 30, terminal 40, etc.), the data conversion server 10. However, based on the viewpoint (second viewpoint) of how to obtain the document data to be converted, it will be described in a plurality of forms.
[0039]
As a first aspect, the conversion processing in the data conversion server 10 can be divided into two forms: a case where the conversion processing is executed asynchronously with respect to a request from the client side, and a case where the conversion processing is executed synchronously. Executing asynchronously means that the response by the data conversion server 10 to the document data conversion request by the terminal 40 is made before the conversion of the document data is completed. “Synchronized and executed” means that the response from the data conversion server 10 to the document data conversion request by the terminal 40 is made after the conversion of the document data is completed.
[0040]
As a second aspect, when the data conversion server 10 acquires document data to be converted from the document management server 20 (PULL type), the document data stored in the terminal 40 by the terminal 40 is converted into the data management server. 10 is uploaded into two forms (PUSH type).
[0041]
By combining the first viewpoint and the second viewpoint, four forms of an asynchronous PULL type, an asynchronous PUSH type, a synchronous PULL type, and a synchronous PUSH type are established. Hereinafter, these four modes will be described in order as first to fourth embodiments.
[0042]
First, as a first embodiment, a case will be described in which document data is converted by asynchronous PULL type processing. 4 and 5 are sequence diagrams for explaining processing of the data conversion system in the first embodiment (asynchronous PULL type). In the sequence diagrams of FIGS. 4 and 5, those that function as communication means such as the httpd 31, the SOAP proxy 33, the SOAP listener 11, the document management connection unit 15, and the SOAP listener 21 are omitted for convenience. The same applies to the subsequent sequence diagrams.
[0043]
In step S11, the user of the terminal 40 selects document data to be converted (hereinafter referred to as “target data”) on the document list page displayed on the Web browser 41, and further defines the conversion process on the setting page. When the parameter information to be set (hereinafter referred to as “conversion parameter information”) is set, the Web browser 41 transmits a target data conversion request to the Web server 30.
[0044]
FIG. 6 is a diagram illustrating a display example of a document list page. The document list page 410 can be displayed on the web browser 41 by inputting the URL of the document list page 410 to the web browser 41. That is, when the Web browser 41 transmits a transmission request for the document list page 410 to the Web server 30 based on the URL input, the Web application 32 of the Web server 30 acquires the document list of the document management unit 22 of the document management server 20. By calling the method by SOAP RPC, the list information of document data in a predetermined folder of the document management DB 23 is acquired. The Web application 32 generates a Web page (document list page 410) on which the acquired document data list information is posted. The document list page 410 generated by the web application 32 is transmitted to the terminal 40 by the httpd 31 and displayed on the web browser 41.
[0045]
In the document list page 410, each document data is displayed as a thumbnail in an area 411. Here, if a rectangular area in which one document data is displayed is called a “cell”, each cell has a check button for selecting the document data, and a document data name (document name). Has a document name display area and an icon display area. For example, a cell in which document data with the document name “Document 3” is displayed includes a check button 413, a document name display area 414, and an icon display area 415.
[0046]
Displayed when the user checks a check button corresponding to the document data to be converted (in FIG. 6, checks Document 1, Document 2, and Document 3) and clicks the document operation menu 412 (not shown). Corresponds to the desired data format among the menu items ("PDF conversion", "Textification", "BITMAP conversion", ".JPEG conversion", "JPEG2000 conversion", "PNG conversion", "TIFF conversion", etc.) When the menu item to be selected is selected, a setting page is displayed on the Web browser 41.
[0047]
FIG. 7 is a diagram illustrating a display example of the setting page. A setting page 420 in FIG. 7 is a setting page displayed when PDF conversion is selected. The setting page 420 is a Web page for setting conversion parameter information in the conversion process, and includes a target data list area 421, a file combination selection area 422, a storage location selection area 423, an archive format selection area 424, and an archive file name input area. 425, a conversion failure operation selection area 426, a priority selection area 427, and the like.
[0048]
The target data list area 421 is an area in which a list of document names of document data selected as target data on the document list page 410 is displayed.
[0049]
The file combination selection area 422 is used to select whether or not to generate converted data (hereinafter referred to as “converted data”) as one file when a plurality of document data is selected as target data. It is an area. The user can make such a selection with the tick button 4221, and in the text box 4222, a file storing one conversion data generated based on a plurality of document data (hereinafter referred to as “combined file”). You can enter a file name.
[0050]
The storage location selection region 423 is a region for selecting a storage location of conversion data. The user can select a predetermined folder or the like in the document management DB 23 as a conversion data storage location using the combo box 4231.
[0051]
The archive format selection area 424 is an area for setting information relating to conversion data archiving. The user can select whether or not to archive using the check button 4221, and can select an archive format using the combo box 4242.
[0052]
The archive file name input area 425 is an area for inputting the file name of the archive file to be generated when the conversion data is archived. The user can input the file name of the archive file in the text box 4251.
[0053]
The conversion failure operation selection area 426 is an area for selecting an operation when the conversion process fails midway due to a failure or the like. The user can select a skip button 4261 and a check button 4262 to execute by skipping or to cancel the conversion. “Skip and execute” means, for example, that if conversion of document 1, document 2 and document 3 is requested, even if conversion of document 1 fails, conversion of document 2 and document 3 is executed as it is. is there.
[0054]
The priority selection area 427 is an area for selecting the priority of the conversion request. The user can select a priority in the combo box 4271. The priority here specifies the order of conversion requests to be processed when the data conversion server 10 processes a plurality of conversion requests. That is, if a high priority is specified, there is a high possibility that the conversion request will be processed quickly. In the present embodiment, the priority is expressed by numbers such as 1, 2, 3, 4,..., And the smaller the value, the higher the priority.
[0055]
When the user sets the conversion parameter information on the setting page 420 and clicks the OK button 428, the Web browser 41 transmits the conversion request in Step S11 described above to the Web server 30 with the conversion parameter information.
[0056]
Progressing to step S12 following step S11, the web application 32 of the web server 30 calls the asynchronous PULL type conversion method which is one of the conversion request reception methods of the conversion job processing unit 12 of the data conversion server 10, thereby asynchronously. Requests conversion of document data in the PULL type.
[0057]
FIG. 8 is a diagram illustrating an example of argument information of an asynchronous PULL type conversion method. As shown in FIG. 8, the asynchronous PULL type conversion method includes the URL of the document management server, the document ID, the combined file name, the storage location, the archive format archive file name, the processing at the time of conversion failure, and the priority as arguments. Have.
[0058]
The URL of the document management server 20 is designated as the URL of the document management server. The document ID is identification information assigned to uniquely identify each document data, and here, the document ID of the target data is designated. That is, for the target data, only the document ID is specified, and the actual data of the target data is not specified as the argument value.
[0059]
The above is information specified based on the setting contents in the document list page 410. Further, the information after the combined file name is information specified based on the setting content on the setting page 420.
[0060]
In the above description, the conversion job processing unit 12 has four types of methods as the conversion request reception method, as is apparent from the expression of the asynchronous PULL type conversion method as “one of the conversion request reception methods”. . One is the above-described asynchronous PULL type conversion method, and the other three are an asynchronous PUSH type conversion method, a synchronous PULL type conversion method, and a synchronous PUSH type conversion method. Each method is for receiving a conversion request by an asynchronous PULL type, an asynchronous PUSH type, a synchronous PULL type, and a synchronous PUSH type. Therefore, the conversion job processing unit 12 identifies synchronous / asynchronous and PUSH / PULL depending on the type of method to be called (depending on the type of conversion request), and executes corresponding processing.
[0061]
In step S13 following step S12, the conversion job processing unit 12 of the data conversion server 10 for which the asynchronous PULL type conversion method has been called temporarily stores the conversion request. Thus, it is requested to save the conversion parameter information specified as an argument of the asynchronous PULL type conversion method as job information of the job to be executed in response to the conversion request.
[0062]
Progressing to step S14 following step S13, the queue access unit 16 registers the job information in the job queue 17.
[0063]
FIG. 9 is a diagram illustrating a configuration example of a job queue. As shown in FIG. 9, the job queue 17 according to the present embodiment includes a top folder 171 and a plurality of queue folders defined under the top folder 171 (priority 1 folder 172, priority 2 folder 173). , And a priority 3 folder 174), a queue information file 175 that is also arranged under the top folder 171, and job files (job file 176, job file 177, and job file generated under the queue folder) 178).
[0064]
One job file is generated for each conversion request and stores job information corresponding to each conversion request.
[0065]
In order to distinguish the priority of each job file, a plurality of queue folders are defined for each priority. That is, each job file is generated under a queue folder corresponding to the priority of the corresponding conversion request.
[0066]
The queue information file 175 is a file that stores information for determining whether there is a currently unprocessed job.
[0067]
Based on the configuration of the job queue 17 described above, job information registration processing by the queue access unit 16 in step S14 will be described in more detail. FIG. 10 is a flowchart for explaining job information registration processing by the queue access unit.
[0068]
The queue access unit 16 first assigns a job ID for uniquely identifying a job (S14a).
[0069]
Subsequently, a job file is generated in the queue folder corresponding to the job priority (conversion request priority), and the job information is registered in the job file. (S14b). For example, when the priority is 1, a job job file is generated under the priority 1 folder 172.
[0070]
FIG. 11 is a diagram illustrating a configuration example of job information stored in a job file. As shown in FIG. 11, the job information is configured by associating the job ID with the argument information (FIG. 8) of the asynchronous PULL type conversion method.
[0071]
In step S14c following step S14b, the queue access unit 16 registers the job ID in the queue information file 175.
[0072]
FIG. 12 is a diagram illustrating a configuration example of the queue information stored in the queue information file. As shown in FIG. 12, the queue information file 175 includes, as queue information, the job ID of the last processed job and the last job ID (that is, the job ID of the job for the last received conversion request). .) Accordingly, here, the queue access unit 16 updates the value of the job ID assigned last to the value of the job ID newly assigned this time. A method for using the queue information will be described later.
[0073]
This completes registration of job information in the job queue 17.
[0074]
Returning to FIG. 4, in step S <b> 15, the queue access unit 16 outputs the job ID of the job registered in the job queue 17 to the conversion job processing unit 12. Here, the conversion job processing unit 12 does not execute the requested conversion process (job) (asynchronous), and transmits the job ID to the Web application 32 as a return value of the asynchronous PULL type conversion method (S16). Note that the job ID is stored in the Web server 30 by the Web application 32 and is used when making an inquiry about the job status.
[0075]
Progressing to step S17 following step S16, the web application 32 transmits a web page (hereinafter referred to as “response page”) indicating that the conversion request has been received to the web browser 41 as a response to the conversion request. The response page is displayed by the web browser 41, and the user can confirm that the conversion request has been received normally.
[0076]
On the other hand, even after the conversion job processing unit 12 responds to the Web application 32 in step S <b> 16, in the data conversion server 10, the asynchronous management unit 14 periodically sets the conversion execution method of the conversion job processing unit 12. (S18). The conversion job processing unit 12 requests the queue access unit 16 to acquire job information from the job queue 17 based on the call by the asynchronous management unit 14 (S19).
[0077]
In step S20 following step S19, the queue access unit 16 refers to the queue information (FIG. 12) stored in the queue information file 175, so that the currently unprocessed job (hereinafter, “unprocessed job”). Whether or not there is) is determined. That is, in the queue information, the values of the job ID of the last processed job (hereinafter referred to as “final job ID”) and the last number of the job ID (hereinafter referred to as “numbered job ID”) are the same. If this is the case, it can be determined that there is no currently unprocessed job. On the other hand, if the two values are different, at least the job corresponding to the numbering job ID has not been processed yet. Therefore, the queue access unit 16 determines whether there is an unprocessed job by comparing the final job ID and the numbered job ID.
[0078]
If it is determined that there is an unprocessed job, the queue access unit 16 searches for job files in order from the queue folder with the highest priority, and acquires job information from the first found job file (S21). The queue access unit 16 outputs the acquired job information to the conversion job processing unit 12 (S22).
[0079]
If it is determined in step S20 that there is no unprocessed job, the queue access unit 16 notifies the conversion job processing unit 12 that there is no unprocessed job. In this case, the processing from step S19 to step S22 is repeatedly executed based on the re-calling from the asynchronous management unit 14.
[0080]
Progressing to step S23 following step S22, the conversion job processing unit 12 issues a transmission request for the target data based on the “document management server URL” and “document ID” in the acquired job information (FIG. 11). The data is transmitted to the document management unit 22 of the document management server 20. The target data transmission request is made by calling a document acquisition method implemented in the document management unit 22 by SOAP RPC via the document management connection unit 15.
[0081]
Progressing to step S24 following step S23, the document management unit 22 acquires the target data from the document management DB 23 and transmits it to the conversion job processing unit 12 (S25).
[0082]
Progressing to step S26 following step S25, the conversion job processing unit 12 stores the received target data in the work folder.
[0083]
FIG. 13 is a diagram illustrating an example of storing target data in a work folder. In FIG. 13, a plurality of folders defined under the work folder 181 are folders corresponding to the respective jobs (hereinafter referred to as “job folders”), and for example, the corresponding job IDs are used as the folder names. .
[0084]
Under each job folder, a Before folder is further defined. The Before folder is a folder for storing target data before conversion.
[0085]
Accordingly, in step S26, the conversion job processing unit 12 sets a job folder (for example, job folder 182) corresponding to the job currently processed (hereinafter referred to as “current job”) under the work folder 181. Further, a Before folder 183 is generated under the job folder 182, and the target data (such as document 1) is stored in the Before folder 183.
[0086]
Progressing to step S27 of FIG. 5 following step S26, the conversion job processing unit 12 converts the target data into the format specified in “data format of conversion destination” in the job information (FIG. 11). 13 is requested.
[0087]
Progressing to step S28 following step S27, the data conversion unit 13 extracts the target data from the Before folder 183, converts the target data into a specified data format (such as PDF), and converts the conversion data generated by the conversion into work And save in the folder 187.
[0088]
FIG. 14 is a diagram illustrating an example of storing the converted data in the working folder. As illustrated in FIG. 14, the data conversion unit 13 generates an After folder 184 under the job folder 182 that is a job folder corresponding to the current job, and stores the converted data under the After folder 184.
[0089]
When the response from the conversion job processing unit 12 is received (S29), the conversion job processing unit 12 retrieves the conversion data from the After folder 184 and calls the document registration method of the document management unit 22 to the document management unit 22. A request is made to register the converted data in the document management DB 23 (S30). Note that the registration destination folder is specified based on the “storage location” of the job information (FIG. 11).
[0090]
Progressing to step S31 following step S30, the document management unit 22 registers the conversion data in the designated folder, and transmits a response to the effect that the conversion data has been registered to the conversion job processing unit 12 (S32).
[0091]
In step S33 following step S32, the conversion job processing unit 12 requests the queue access unit 16 to delete the job information of the current job from the job queue 17 because the job processing has been normally completed. .
[0092]
Progressing to step S34 following step S33, the queue access unit 16 deletes the job information of the current job from the job queue 17 by deleting the job file (FIG. 10) corresponding to the current job. Further, the queue access unit 16 updates the value of “job ID of the last processed job” in the queue information file 175 to the value of the job ID of the current job, and completes the data conversion process.
[0093]
As described above, according to the data conversion server 10 in the first embodiment, conversion of document data can be executed based on a request from the terminal 40. Therefore, it is not necessary to install a program corresponding to the data conversion unit 13 necessary for document data conversion for each terminal.
[0094]
Since one data conversion server 10 corresponds to a plurality of terminals 40, causing the data conversion server 10 to execute conversion processing can improve resource efficiency in the entire system and enhance the function of the data conversion unit 13. And can be flexibly adapted to version upgrades.
[0095]
In addition, since the data conversion server 10 in the first embodiment acquires document data by the PULL type, it can be used without inconvenience even from a mobile phone or the like that is not suitable for handling large data.
[0096]
Further, since the data conversion server 10 in the first embodiment executes the conversion process asynchronously with respect to the terminal 40, the Web browser 41 of the terminal 40 that has requested conversion of the document data waits for a response to the conversion request. It is possible to return early from this state. Therefore, the user of the Web browser 41 can perform another work in the Web browser 41 without waiting for a long time after making a document data conversion request. That is, it is possible to prevent an adverse effect of an increase in waiting time until the conversion process is completed, which can be caused by performing the conversion process in the data conversion server 10 in an integrated manner.
[0097]
Furthermore, since the data conversion server 10 controls the order in which the conversion requests are processed according to the priority, the data conversion server 10 can execute the conversion process flexibly corresponding to the urgency level or the like.
[0098]
Next, as a second embodiment, a case where document data is converted by asynchronous PUSH type processing will be described. FIGS. 15 and 16 are sequence diagrams for explaining the processing of the data conversion system in the second embodiment (asynchronous PUSH type).
[0099]
When the user of the terminal 40 sets the target data and the conversion parameter information on the setting page for PUSH type (hereinafter referred to as “PUSH setting page”) displayed on the Web browser 41, the terminal 40 sends the information to the Web server 30. On the other hand, the target data conversion request is transmitted, and the actual data of the target data is uploaded to the Web server 30 (S41).
[0100]
FIG. 17 is a diagram illustrating a display example of a setting page for PUSH. The PUSH setting page 430 in FIG. 17 has substantially the same configuration as the setting page 420 (FIG. 7), but a target data selection area 431 is arranged instead of the target data list area 421 in the setting page 420. It is different in point.
[0101]
The target data selection area 431 is an area for selecting target data from document data stored in the terminal 40. When the user clicks the file selection button 4312, a file dialog is displayed, and the document name of the document data selected on the file dialog is displayed in the text box 4311 and recognized as target data.
[0102]
Accordingly, when the user selects document data as the target data on the PUSH setting page 430, sets other conversion parameter information, and clicks the OK button 432, the process of step S41 described above is executed.
[0103]
Progressing to step S42 following step S41, the web application 32 of the web server 30 requests conversion of document data by calling the asynchronous PUSH type conversion method of the conversion job processing unit 12 of the data conversion server 10.
[0104]
FIG. 18 is a diagram illustrating an example of argument information of an asynchronous PUSH type conversion method. As shown in FIG. 18, the argument information of the asynchronous PUSH type conversion method is almost the same as the argument information of the asynchronous PULL type conversion method (FIG. 8), but in that it has actual data of the target data instead of the document ID. Different. Therefore, in step S24, the Web application 32 designates the actual data of the target data uploaded from the Web browser 41 as the value of the argument and calls the asynchronous PUSH type conversion method. It is transmitted to the conversion device 10.
[0105]
Progressing to step S43 following step S42, the conversion job processing unit 12 for which the asynchronous PUSH type conversion method has been called sends the queue access unit 16 the conversion parameters specified as arguments of the asynchronous PUSH type conversion method as job information. Request to save information.
[0106]
In step S44 following step S43, the queue access unit 16 registers the job information in the job queue 17 (FIG. 10) by the same procedure as described in the first embodiment (FIG. 9), and the job The ID is output to the conversion job processing unit 12 (S45). However, the configuration of the job information stored in the job file is slightly different from that in the first embodiment (FIG. 11).
[0107]
FIG. 19 is a diagram illustrating a configuration example of job information stored in a job file according to the second embodiment. As shown in FIG. 19, the job information in the second embodiment does not include a document ID. This is because in the second embodiment, since the actual data of the target data has already been uploaded, it is not necessary to identify the target data by the document ID. Further, the job information in the second embodiment has “target data storage location” instead of “document management server URL”. “Target data storage location” means a path name or the like of a location for storing uploaded target data.
[0108]
Progressing to step S46 following step S45, the conversion job processing unit 12 converts the actual data of the target data specified as the argument of the asynchronous PUSH type conversion method into the Before of the working folder 181 as in step S26 (FIG. 4). Save it to a folder ("Target data storage location").
[0109]
Subsequent to step S46, the process proceeds to step S47, and thereafter, from step S16 to step S35 (FIGS. 4 and 5) in the first embodiment, the same processing as step S62 in FIG. In the second embodiment, the process for acquiring target data from the document management server 20 (FIG. 4: S23 to S26) is not executed, as described above, the target data has already been uploaded to the data conversion server 10, This is because it is stored in the working folder 181.)
[0110]
That is, at this point, the conversion job processing unit 12 does not execute the requested conversion process (asynchronous) and transmits the job ID to the Web application 32 (S47). A response page is transmitted to the web browser 41 by the web application 32 and displayed on the web browser 41 (S48).
[0111]
Further, based on the periodic call by the asynchronous management unit 14 (S49), the conversion job processing unit 12 acquires the job information registered in the job queue 17 from the queue access unit 16 (S50 to S53), and the job Based on the information, the data conversion unit 13 is caused to execute conversion processing of the target data that has already been uploaded and saved in the work folder (S54 to S56).
[0112]
Subsequently, the conversion job processing unit 12 registers the conversion data in the document management DB 23 by transmitting the conversion data generated by the conversion processing to the document management unit 22 (S57 to S59), and performs a job in the queue access unit 16. The job information of the current job is deleted from the queue 17 (S60 to S62).
[0113]
As described above, according to the data conversion server 10 in the second embodiment, conversion processing of document data can be executed based on a request from the terminal 40, and therefore in the first embodiment. Similar to the data conversion server 10, the resource efficiency of the entire system can be increased, and the function enhancement of the data conversion unit 13 can be flexibly dealt with.
[0114]
In addition, since the data conversion server 10 according to the second embodiment sets document data uploaded from the terminal 40 as the conversion target of the document data, the user can use the document data generated or edited in the terminal 40 as it is (document It can be designated as a conversion target (without going through operations such as registration to the management server 20), and a document data conversion request can be easily made.
[0115]
Furthermore, since the data conversion system 1 in the second embodiment generates print data asynchronously with respect to the terminal 40, the Web browser 41 of the terminal 40 that has requested conversion of document data waits for a response to the conversion request. It is possible to return early from this state. Therefore, the user of the Web browser 41 can perform another operation in the Web browser 41 without waiting after making a document data conversion request.
[0116]
Next, a case where document data is converted by synchronous PULL type processing will be described as a third embodiment. 20 and 21 are sequence diagrams for explaining processing of the data conversion system in the third embodiment (synchronous PULL type). Since the third embodiment is common to the first embodiment in that it is a PULL type, the processing procedure has much in common with the first embodiment. Therefore, the difference from the first embodiment (FIGS. 4 and 5) will be mainly described.
[0117]
From step S71 to step S75, processing substantially similar to that from step S11 to step S15 in the first embodiment is executed. That is, the conversion parameter information set on the setting page (FIG. 7) is transmitted from the Web browser 41 to the Web application 32 via the document list page 410 (FIG. 6) (S71). The conversion request reception method is called (S72). However, in step S72, the synchronous PULL type conversion method is called instead of the asynchronous PULL type conversion method in the first embodiment. The argument information of the synchronous PULL type conversion method is the same as that of the asynchronous PULL type conversion method.
[0118]
The conversion job processing unit 12 that has been called the synchronous PULL type conversion method registers the job information in the job queue 17 using the queue access unit 16 (S73 to S75).
[0119]
Progressing to step S76 following step S75, the conversion job processing unit 12 waits for completion of a data conversion process to be described later without making a response to the web application 32 at this point.
[0120]
Subsequent to step S76, the process proceeds to step S77, and thereafter, the same processing as that from step S18 to step S35 (FIGS. 4 and 5) in the first embodiment is executed up to step S94.
[0121]
That is, based on the periodic conversion execution method call by the asynchronous management unit 14 (S77), the conversion job processing unit 12 acquires job information registered in the job queue 17 from the queue access unit 16 (S78-). In step S81, the target data is acquired from the document management unit 32 based on the job information (S82 to S85). Subsequently, the conversion job processing unit 12 causes the data conversion unit 13 to execute conversion processing of the target data (S86 to S88), and transmits the conversion data generated by the conversion processing to the document management unit 22, thereby converting the conversion data. Is registered in the document management DB 23 (S89 to S91), and the queue access unit 16 deletes the job information of the current job from the job queue 17 (S92 to S94).
[0122]
It should be noted that the process (or thread, hereinafter simply referred to as “process”) that executes the processing from step S77 to step S94 is different from the process that waits in step S76. That is, the former process (hereinafter referred to as “conversion execution process”) is a process to which the asynchronous management unit 14 belongs, whereas the latter process (hereinafter referred to as “waiting process”) is synchronized in step S72. It is a process that is activated based on the invocation of a PULL type conversion method. This point is the same in the first embodiment, but in the third embodiment, the waiting process is performed in step S76. In the sequence diagrams of FIGS. 20 and 21, the waiting process is performed. Since the conversion job processing unit 12 being performed and the conversion job processing unit 12 related to the processing from step S77 to step S94 are indicated by the same axis, the processes are different for understanding the relationship between the two. It is necessary to confirm that.
[0123]
Progressing to step S95 following step S94, the conversion job processing unit 12 in the conversion execution process notifies the waiting process that conversion processing has been completed (conversion processing completion notification).
[0124]
Progressing to step S96 following step S95, the conversion job processing unit 12 in the waiting process that has received the notification of completion of the conversion process sends a response (return value) to the call of the synchronous PULL type conversion method in step S72 to the Web application 32. To send. Note that the synchronous PULL type conversion method is less required to be sent to the Web application 32 by including the job ID in the response than the asynchronous PULL type conversion method. This is because the Web application 32 receives the response after the conversion process is completed and the success or failure is revealed, and it is not necessary for the Web application 32 to inquire the job status to the data management server 10 thereafter. . Therefore, the return value of the synchronous PULL type conversion method may be only information indicating whether or not the conversion process has been normally completed.
[0125]
Proceeding to step S97 following step S96, the web application 32 transmits, to the web browser 41, a web page notifying that the conversion process has been completed (hereinafter referred to as “completion notification page”) as a response to the conversion request. . The completion notification page is displayed by the web browser 41. Note that the processing in step S97 corresponds to the processing in step S17 (FIG. 4) in the first embodiment. However, the response page transmission in step S17 is executed before the conversion process is executed, whereas the completion notification page transmission in step S97 is executed after the conversion process is completed. Therefore, the user who browsed the completion notification page confirms that the conversion process has been completed, not that the conversion request has been accepted.
[0126]
As described above, according to the data conversion server 10 in the third embodiment, the conversion process can be executed based on the request from the terminal 40 for the conversion of the document data. Similarly to the data conversion server 10 in the form, the resource efficiency of the entire system can be increased and the function enhancement of the data conversion unit 13 can be flexibly dealt with.
[0127]
In addition, since the data conversion server 10 according to the third embodiment acquires document data by the PULL type, it can be used without inconvenience even from a mobile phone that is not suitable for handling large data.
[0128]
Furthermore, since the data conversion sub-field 10 in the third embodiment executes document data conversion processing in response to a conversion request from the terminal 40, the user of the terminal 40 converts the document data. Can be confirmed on the spot.
[0129]
Note that when the processing is executed synchronously as in the third embodiment, the calling processing by the asynchronous management unit 14 is not necessarily required. In other words, the conversion job processing unit 12 in the waiting process may execute the processes in and after step S78 without performing the waiting process in step S76. However, by taking the procedure that the conversion job processing unit 12 executes the conversion process based on the call of the asynchronous management unit 14, the affinity between the synchronous type procedure and the asynchronous type procedure can be enhanced. Therefore, the source code can be shared, and the development efficiency can be improved. For this reason, in the third embodiment, the waiting process waits for the completion of the conversion process (S76), and the conversion execution process executes the conversion process based on the call of the asynchronous management unit 14. Is adopted. This also applies to the fourth embodiment described later.
[0130]
Next, a case where document data is converted by synchronous PUSH type processing will be described as a fourth embodiment. 22 and 23 are sequence diagrams for explaining the processing of the data conversion system in the fourth embodiment (synchronous PUSH type).
[0131]
From step S101 to step S106, processing similar to that from step S41 to step S46 (FIG. 15) in the second embodiment taking the same PUSH type is executed. That is, together with the conversion parameter information set on the PUSH setting page 430, the document data stored in the terminal 40 is uploaded to the data conversion server 10 as target data (S101, S102). However, in step S102, the synchronous PUSH type conversion method is called instead of the asynchronous PUSH type conversion method in the second embodiment. The argument information of the synchronous PUSH type conversion method is the same as that of the asynchronous PUSH type conversion method.
[0132]
The conversion job processing unit 12 that has called the synchronous PUSH type conversion method registers the job information in the job queue 17 using the queue access unit 16 (S103 to S105), and uploads the target data to the work folder 181. Save (S106).
[0133]
Subsequent to step S106, the process proceeds to step S107, and thereafter, the same processing as that from step S76 to step S97 (FIGS. 20 and 21) in the third embodiment taking the same synchronization type is executed until step S124 (FIG. 20 and FIG. 21). However, in the fourth embodiment, the process of acquiring target data from the document management server 20 (FIG. 20: S82 to S85) is not executed, as described above, the target data has already been uploaded to the data conversion server 10. This is because it is stored in the working folder 181.)
[0134]
That is, the conversion job processing unit 12 in the waiting process waits for conversion processing (S107).
[0135]
Based on the periodic conversion execution method call by the asynchronous management unit 14 (S108), the conversion job processing unit 12 in the conversion execution process acquires the job information registered in the job queue 17 from the queue access unit 16 ( S109 to S112), based on the job information, the data conversion unit 13 is caused to execute the target data conversion process (S113 to S115).
[0136]
Subsequently, the conversion job processing unit 12 registers the conversion data in the document management DB 23 by transmitting the conversion data generated by the conversion processing to the document management unit 22 (S116 to S118), and performs a job in the queue access unit 16. The job information of the current job is deleted from the queue 17 (S119 to S121).
[0137]
When the conversion job processing unit 12 in the conversion execution process notifies the waiting process of the completion of the conversion processing, the conversion job processing unit 12 in the waiting process sends a response (return value) to the call of the synchronous PUSH type conversion method in step S102 to the Web application 32. Note that the return value of the synchronous PULL type conversion method may be only information indicating whether or not the conversion process has been normally completed, as with the return value of the synchronous PULL type method in the third embodiment.
[0138]
As a response to the conversion request, the web application 32 transmits a completion notification page to the web browser 41, and the completion notification page is displayed by the web browser 41 (S124). The user who browsed the completion notification page can confirm that the conversion process has been completed.
[0139]
As described above, according to the data conversion server 10 in the fourth embodiment, the conversion processing of document data can be executed based on a request from the terminal 40, and thus the other embodiments described above. As with the data management server 10 in FIG. 1, the resource efficiency of the entire system can be increased and the function enhancement of the data conversion unit 13 can be flexibly dealt with.
[0140]
In addition, since the data conversion server 10 according to the fourth embodiment uses the document data uploaded from the terminal 40 as a conversion target, the user can directly convert the document data generated or edited in the terminal 40 into the document data conversion target. The document data conversion request can be easily made.
[0141]
Furthermore, since the data conversion server 10 in the fourth embodiment executes document data conversion processing synchronously with the terminal 40, the user of the terminal 40 confirms that the conversion of the document data has been completed on the spot. Can be confirmed.
[0142]
Note that the above-described four embodiments are not in an exclusive relationship with each other, and implementations in the four forms may coexist. For example, the PUSH type and PULL type selection is arbitrarily determined by the user. That is, when the Web page to be used is different between the PULL type and the PUSH type as in the present embodiment, the PULL type / PUSH is selected depending on which Web page is displayed by the user.
[0143]
On the other hand, the selection of the synchronous type or the asynchronous type may be specified with a check button or the like on the setting page 410 or the setting page 420 for PUSH, or the data conversion server 10 may be automatically determined. . In the latter case, for example, when document data conversion requests are received from a plurality of terminals at the same time and the load of the data conversion server 10 is high, or the size of the document data to be converted is a predetermined value or more. If it takes a long time to complete the processing, the processing is performed in a short time such as when the load on the data conversion server 10 is low or the size of the document data to be converted is small. If the process can be completed, it may be a synchronous type.
[0144]
Furthermore, in the above-described embodiment, the example in which the Web server 30, the data conversion server 10, and the document management server 20 are configured by independent hardware has been described. However, all functions are implemented in one server machine. Alternatively, an independent server may be set up in smaller functional units.
[0145]
The preferred embodiments of the present invention have been described in detail above, but the present invention is not limited to such specific embodiments, and various modifications can be made within the scope of the gist of the present invention described in the claims.・ Change is possible.
[0146]
【The invention's effect】
As described above, according to the present invention, it is possible to provide a data format conversion function via a network.
[Brief description of the drawings]
FIG. 1 is a diagram illustrating a configuration example of a data conversion system according to an embodiment of the present invention.
FIG. 2 is a diagram illustrating a hardware configuration example of a data conversion server in the embodiment of the present invention.
FIG. 3 is a diagram illustrating a functional configuration example of a data conversion system according to an embodiment of the present invention.
FIG. 4 is a sequence diagram for explaining processing of the data conversion system in the first embodiment (asynchronous PULL type);
FIG. 5 is a sequence diagram for explaining processing of the data conversion system in the first embodiment (asynchronous PULL type);
FIG. 6 is a diagram illustrating a display example of a document list page.
FIG. 7 is a diagram illustrating a display example of a setting page.
FIG. 8 is a diagram illustrating an example of argument information of an asynchronous PULL type conversion method.
FIG. 9 is a diagram illustrating a configuration example of a job queue.
FIG. 10 is a flowchart for explaining job information registration processing by a queue access unit;
FIG. 11 is a diagram illustrating a configuration example of job information stored in a job file.
FIG. 12 is a diagram illustrating a configuration example of queue information stored in a queue information file.
FIG. 13 is a diagram illustrating an example of saving target data in a work folder.
FIG. 14 is a diagram illustrating an example of storing converted data in a working folder.
FIG. 15 is a sequence diagram for explaining processing of the data conversion system in the second embodiment (asynchronous PUSH type);
FIG. 16 is a sequence diagram for explaining processing of the data conversion system in the second embodiment (asynchronous PUSH type);
FIG. 17 is a diagram illustrating a display example of a setting page for PUSH.
FIG. 18 is a diagram illustrating an example of argument information of an asynchronous PUSH type conversion method.
FIG. 19 is a diagram illustrating a configuration example of job information stored in a job file according to the second embodiment.
FIG. 20 is a sequence diagram for explaining processing of the data conversion system in the third embodiment (synchronous PULL type).
FIG. 21 is a sequence diagram for explaining processing of the data conversion system in the third embodiment (synchronous PULL type);
FIG. 22 is a sequence diagram for explaining processing of the data conversion system in the fourth embodiment (synchronous PUSH type);
FIG. 23 is a sequence diagram for explaining processing of the data conversion system in the fourth embodiment (synchronous PUSH type);
[Explanation of symbols]
1 Data conversion system
10 Data conversion server
11, 21 SOAP Listener
12 Conversion job processing section
13 Data converter
14 Asynchronous Management Department
15 Document management connection
16 Queue access unit 16
17 Job queue
20 Document management server
22 Document Management Department
23 Document Management DB
30 Web server
31 httpd
32 Web application
33 SOAP proxy
40 terminals
41 Web browser
100 drive device
101 storage medium
102 Auxiliary storage device
103 Memory device
104 arithmetic processing unit
105 Interface device
B bus

Claims (23)

A data conversion device having data conversion means for converting the data format of predetermined data,
A communication means for receiving a conversion request of a data format of the predetermined data transmitted via a network;
A data conversion apparatus comprising: conversion request processing means for causing the data conversion means to convert the data format of the predetermined data based on the conversion request received by the communication means. The conversion request processing means has a conversion method for receiving the conversion request,
The data conversion apparatus according to claim 1, wherein the conversion request is a call request for the conversion method. 3. The data conversion apparatus according to claim 2, wherein the call request for the conversion method is based on SOAP RPC. The conversion request processing unit causes the communication unit to transmit a response to the conversion request before causing the data conversion unit to convert the data format of the predetermined data according to the type of the conversion request. Item 4. The data conversion device according to any one of Items 1 to 3. The conversion request processing means causes the communication means to transmit a response to the conversion request after the data conversion means converts the data format of the predetermined data according to the type of the conversion request. Item 4. The data conversion device according to any one of Items 1 to 3. Job information management means for managing job information related to conversion processing based on the conversion request;
The conversion request processing means includes job information registration means for registering information included in the conversion request as the job information in the job management means,
Job processing means for periodically acquiring the job information from the job information management means and causing the data conversion means to convert the data format of the predetermined data based on the acquired job information. The data conversion apparatus according to claim 1. The job information registration unit registers the job information in the job management unit in accordance with the type of the conversion request, and then waits for the conversion unit to convert the data format of the predetermined data to the communication unit without waiting for the conversion. The data conversion apparatus according to claim 6, wherein a response to the conversion request is transmitted. The job information registration unit registers the job information in the job management unit in accordance with the type of the conversion request, and after the conversion of the data format of the predetermined data by the conversion unit is completed, the job information registration unit converts the job information into the communication unit. 8. The data conversion apparatus according to claim 6, wherein a response to the request is transmitted. The job information management means manages the job information according to the priority of the conversion request included in the conversion request,
The data conversion apparatus according to claim 6, wherein the job processing unit processes the conversion request with a high priority. The job information management means has a plurality of folders defined for each priority,
The job information registration means registers the job information in the folder according to the priority of the conversion request,
The data conversion apparatus according to claim 9, wherein the job processing unit acquires the job information in order from the folder with the highest priority. Managing first job identification information that is job identification information of job information for the last received conversion request, and second job identification information that is job identification information of job information for the last processed conversion request. A job identification information management means;
The job processing unit acquires the job information when the first job identification information and the second job identification information acquired from the job identification information management unit are the same. Item 11. The data conversion device according to any one of Items 6 to 10. Further comprising data acquisition means for acquiring the predetermined data based on data identification information of the predetermined data;
The conversion request processing means, when the predetermined data is not included in the conversion request, the data acquisition means of the predetermined data acquired based on the data identification information included in the conversion request 12. A data conversion apparatus according to claim 1, wherein the data format is converted by the conversion means. 13. The data conversion apparatus according to claim 12, wherein the data acquisition unit acquires the predetermined data from a first data management apparatus connected via a network. 12. The conversion request processing unit, when the predetermined data is included in the conversion request, causes the conversion unit to convert the data format of the data. Data converter. The conversion data registration means for registering the conversion data generated by converting the predetermined data by the conversion means in a second data management server connected via a network. The data conversion device according to any one of 1 to 14. A data conversion method in a data conversion device for converting the data format of predetermined data,
A communication procedure for receiving a conversion request of a data format of the predetermined data transmitted via a network;
A data conversion procedure for converting the data format of the predetermined data based on the conversion request;
A data transmission method comprising: a response transmission procedure for transmitting a response to the conversion request before the conversion of the data format of the predetermined data is performed in the data conversion procedure according to the type of the conversion request. . 17. The data according to claim 16, wherein the response transmission procedure transmits a response to the conversion request after the conversion of the predetermined data format in the data conversion procedure is completed according to the type of the conversion request. Conversion method. The conversion request receiving procedure registers job information related to conversion processing based on the received conversion request in a predetermined storage area,
The data conversion procedure includes:
A job information acquisition procedure for periodically acquiring the job information from the predetermined storage area;
A job execution procedure for converting the data format of the predetermined data based on the job information acquired in the job information acquisition procedure;
The response transmission procedure converts the data format of the predetermined data in the job execution procedure after the job information is registered in the predetermined recording area in the conversion request reception procedure according to the type of the conversion request. The data conversion method according to claim 16 or 17, wherein a response to the conversion request is transmitted without waiting. The response transmission procedure waits for the conversion of the data format of the predetermined data in the job execution procedure according to the type of the conversion request, and transmits a response to the conversion request. The data conversion method according to claim 1. A data acquisition procedure for acquiring the predetermined data based on data identification information of the predetermined data;
In the data conversion procedure, when the predetermined data is not included in the conversion request, the data conversion procedure includes the step of the predetermined data acquired based on the data identification information included in the conversion request in the data acquisition procedure. 20. The data conversion method according to claim 16, wherein the data format is converted. 21. The data conversion method according to claim 16, wherein the data conversion procedure converts the data format of the data when the predetermined data is included in the conversion request. To a data conversion device that converts the data format of predetermined data,
A communication procedure for receiving a conversion request of a data format of the predetermined data transmitted via a network;
A data conversion procedure for converting the data format of the predetermined data based on the conversion request;
A data conversion program for executing a response transmission procedure for transmitting a response to the conversion request before the conversion of the data format of the predetermined data is performed in the data conversion procedure according to the type of the conversion request. To a data conversion device that converts the data format of predetermined data,
A communication procedure for receiving a conversion request of a data format of the predetermined data transmitted via a network;
A data conversion procedure for converting the data format of the predetermined data based on the conversion request;
A data conversion program for executing a response transmission procedure for transmitting a response to the conversion request before the data conversion of the predetermined data is performed in the data conversion procedure according to the type of the conversion request. Computer-readable recording medium.

Images