JP2014160484A - Control method for controller - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide the control method of a controller and the controller capable of simplifying the development of an application, and improving processing performance on device control.SOLUTION: A method for controlling a controller includes: a step of receiving a processing request from an application 1; a step of, when the received processing request is an initialization request, determining whether or not the request is a first initialization request after the activation of the application 1; a step of, when the received processing request is the first initialization request, transmitting the request to a device driver 3; a step of storing initialization setting information indicating the state after the initialization processing of the device driver 3; a step of detecting the state of the device driver 3; a step of, when an error is generated in the device driver 3, performing restoration processing based on the state; and a step of, when the device driver 3 is restored, making a request for setting the state of the device driver 3 to the state based on the initialization setting information.

Description

  The present invention relates to a controller control method and a controller that are interposed between an application and a device driver and function as a software module for controlling the device driver.

  Conventionally, when a device (for example, a printer) connected to a computer is controlled, control is performed using a device driver corresponding to the device (for example, see Patent Document 1). In general, such a device driver provides a number of interfaces for controlling the corresponding device. When an application program (hereinafter referred to as an application) is developed, the interface provided by the device driver is used. By creating a program, it is possible to execute delicate error processing according to the state of the device, including basic operation control of the device.

JP-A-11-265267

However, in the case of controlling a device as described above, in general, a large number of functions and various types of error handling caused by the device are defined to control the device. When delicate error processing is performed using, there is a problem that the processing flow of the application becomes complicated. For this reason, there is a problem that the cost for application development becomes high.
On the other hand, batch processing is performed to avoid complicating the processing flow of the application, and when an error occurs, the cause of the error and the state of the device driver are ignored, and the device driver is always initialized completely. There are cases where error handling is performed. However, since the initialization process of the device driver generally takes time, there is a problem that the performance of the device driver is deteriorated by performing the initialization process every time as an error process.

  In view of the above problems, an object of the present invention is to provide a controller control method and a controller that can simplify the development of an application and can improve the processing performance for controlling a device.

  The controller control method of the present invention is a software module that is interposed between an application and a device driver, transfers a processing request from the application to the device driver, and transfers a response to the processing request from the device driver to the application. In the controller control method, a processing request reception step for receiving a processing request from an application, and when the received processing request is an initialization request, the initialization request is the first initialization request after the application is started If the initialization request is the first initialization request as a result of the determination in the initialization request determination step and the initialization request determination step, the initialization request is transmitted to the device driver. Send request step and first Initialization setting information indicating a state after initialization processing of the device driver based on the initialization request is acquired from the device driver, and an initialization setting information storing step for storing the initialization setting information and a state of the device driver are detected. In the state detection step and the state detection step, when it is detected that an error has occurred in the device driver, the return processing step for executing the return processing based on the state of the device driver, and the device driver returned from the error by the return processing In this case, there is provided an initialization setting request step for transmitting a request for setting the state of the device driver to a state based on the stored initialization setting information to the device driver.

  The controller of the present invention is a software module that is interposed between an application and a device driver, and transfers a processing request from the application to the device driver, and transfers a response to the processing request from the device driver to the application. If a certain controller is a processing request receiving means for receiving a processing request from an application, and the received processing request is an initialization request, whether or not the initialization request is the first initialization request after the application is started An initialization request determining means for determining, and an initialization request processing means for transmitting the first initialization request to the device driver when the initialization request is the first initialization request as a result of the determination in the initialization request determining means. Device device based on initial initialization request Initialization setting information acquisition means for acquiring initialization setting information indicating a state after initialization processing of the device from the device driver, initialization setting information storage means for storing the acquired initialization setting information, and the status of the device driver. When the state detection means for detecting and the state detection means detect that an error has occurred in the device driver, the return processing means for executing the return processing based on the state of the device driver, and the device driver from the error by the return processing Initialization setting requesting means for transmitting a request for setting the state of the device driver to a state based on the stored initialization setting information when returning, to the device driver.

According to these configurations, when an error occurs in the device driver, the controller can execute an appropriate return process (error process) according to the state of the device driver (according to the error content). This eliminates the need for delicate error processing on the application side, thereby simplifying the application processing flow and reducing the cost of application development.
Also, the controller stores the device driver status (initialization setting information) after the initial initialization process, and after the device driver recovers from the error, the device driver status based on this initialization setting information Can be brought into a state equivalent to that after the initialization process. This eliminates the need for long-time initialization processing such as communication and instance initialization.For example, by introducing the controller of the present invention into an application that performs initialization processing by error processing, processing performance can be improved. Can be improved.

  In the controller control method of the present invention, if the received initialization request is not the first initialization request as a result of the determination in the initialization request determination step, the initialization request is not transmitted to the device driver, and the device driver status In response, it is preferable to return a response to the initialization request to the application.

  In the controller of the present invention, the initialization request processing means may send the initialization request to the device driver when the received initialization request is not the first initialization request as a result of the determination by the initialization request determining means. First, it is preferable to return a response to the initialization request to the application according to the state of the device driver.

  According to these configurations, the controller does not bridge the initialization request from the application to the device driver, and returns a response to the initialization request by itself. That is, the initialization process provided by the device driver (the process of actually initializing communication and instances) is not executed. Thus, for example, the controller of the present invention is introduced to an application that requires initialization processing at a predetermined timing in order to execute the same device control processing every time or an application that performs initialization processing by error processing. As a result, the processing performance can be improved.

  In the controller of the present invention, it is preferable that the input / output interface of the controller has either the same specification as the input / output interface of the device driver or a specification that extends the input / output interface of the device driver.

  According to this configuration, the controller provides an input / output interface having the same specification as the input / output interface of the device driver or an expanded specification. As a result, application developers do not need to learn input / output interfaces with new specifications, and can develop with the same feeling as using the input / output interfaces provided by existing device drivers. , Without reducing application development efficiency.

  In the controller of the present invention, the processing request is preferably a definition of a plurality of processing requests collectively.

  In the controller of the present invention, it is preferable that the plurality of processing requests are defined in a markup language.

  According to these configurations, for example, even in an application that cannot define error processing (error handling) delicately, such as an application that collectively defines a plurality of processing requests in XML (Extensible Markup Language) and performs batch processing, By introducing the controller of the present invention, it is possible to perform appropriate error processing, so that it is easy to realize an application that performs such batch processing.

It is a block diagram which shows the structure of the component model concerning this embodiment. It is a functional block diagram of a controller. It is a sequence diagram explaining an example of the processing of the controller when targeting an application that performs rough error processing. It is a sequence diagram explaining an example of the processing of the controller when targeting an application that does not perform error processing. FIG. 10 is a sequence diagram for explaining an example of a process of a controller when an application that initializes a device driver for each fixed process is targeted.

  Hereinafter, a component model including a controller of the present invention will be described with reference to the accompanying drawings. FIG. 1 is a block diagram showing the configuration of the component model CM of this embodiment. As shown in the figure, the component model CM includes an application 1, a controller 2, and a device driver 3. The application 1, the controller 2, and the device driver 3 are realized as software modules (programs) that operate on an OS (Operating System) installed in the computer.

  The application 1 is a processing request for causing a device (for example, a printer, not shown) connected to a computer to execute a predetermined operation, a processing request for error processing when an error occurs in the processing of the device driver 3, etc. It is a program that performs. These processing requests are defined using an input / output interface (first input / output interface 11) provided by the controller 2, and the application 1 transmits each processing request to the controller 2 and the controller 2 A response to each processing request (success / failure of processing, etc.) is received.

  The controller 2 is a software module interposed between the application 1 and the device driver 3, and transfers (bridges) a processing request from the application 1 to the device driver 3 and sends a response to the processing request from the device driver 3. It is transferred (bridged) to the application 1. Specifically, the controller 2 provides the first input / output interface 11 to the application 1. By using the first input / output interface 11, the controller 2 receives a processing request from the application 1, In addition, a response to the processing request to the application 1 is performed. Further, the controller 2 uses the input / output interface (second input / output interface 12) provided by the device driver 3 to transfer the processing request from the application 1 to the device driver 3 and to respond to the processing request from the device driver 3. Receive.

  The device driver 3 is a program for controlling a target device, and is created based on the specifications of each device. The device driver 3 provides the second input / output interface 12 to the controller 2, receives a processing request from the controller 2 using the second input / output interface 12, and In response to the processing request.

  Note that the specification of the first input / output interface 11 provided by the controller 2 is the same as the specification of the second input / output interface 12 provided by the device driver 3 or a specification obtained by extending the second input / output interface 12 (for example, in XML). It is preferable that the specification is extended so as to correspond. As a result, the application developer does not need to learn the specifications of the new input / output interface, and can develop with the same feeling as using the input / output interface provided by the conventional device driver 3. Therefore, the development efficiency of the application 1 is not reduced.

  Next, the functional configuration of the controller 2 will be described with reference to the functional block diagram of FIG. The controller 2 includes a processing request receiving unit 21, a request processing unit 22, a response processing unit 23, an initialization setting information acquisition unit 24, an initialization setting information storage unit 25, a state detection unit 26, a return processing unit 27, and an initialization setting. Request means 28 is provided.

  The processing request receiving unit 21 functions as a unit that receives a processing request from the application 1. The request processing unit 22 functions as a unit that performs appropriate processing based on the content of the processing request received from the application 1 and the state of the device driver 3. Specifically, when the processing request from the application 1 is an initialization request, it is determined whether or not the initialization request is the first initialization request after the application 1 is activated (initialization request determination means). If the result of this determination is the first initialization request, the first initialization request is transmitted to the device driver 3 (initialization request processing means). On the other hand, if it is not the first initialization request, the initialization request is not bridged (transmitted) to the device driver 3 and a response to the initialization request is returned to the application 1 according to the state of the device driver 3 (initialization request processing) means).

  When the processing request is an end processing request for finishing a series of processing, the end processing request is not bridged to the device driver 3 and a response indicating the success of the processing is returned to the application 1. Further, when the processing request is other than the above-described initialization request and end processing request (hereinafter referred to as “normal processing request”) and the device driver 3 is operating normally, the normal processing request When the device driver 3 is bridged and an error has occurred in the device driver 3, the normal processing request is not bridged to the device driver 3, and a response indicating failure of the normal processing request is returned to the application 1.

  The response processing unit 23 functions as a unit that receives a response to the processing request from the device driver 3 and transmits it to the application 1. That is, it functions as a means for bridging the response from the device driver 3 to the application 1.

  The initialization setting information acquisition unit 24 functions as a unit for acquiring initialization setting information from the device driver 3. This initialization setting information is a state after the device driver 3 executes an initialization process (a process for actually initializing communication and instances) in response to an initial initialization request from the application 1 (hereinafter, this state is referred to as “ This is information indicating “initialized state”. The initialization setting information storage unit 25 functions as a unit that stores (saves) the acquired initialization setting information.

  The state detection unit 26 functions as a unit for detecting the state of the device driver 3, sets the state of itself (controller 2) based on a response to the processing request from the device driver 3, and confirms this state. Thus, the state of the device driver 3 is indirectly detected. Specifically, if the response to the processing request from the device driver 3 is a response indicating the success of the processing, the device driver 3 sets the own state to a normal state and confirms this state (normal state). Detects normal state. On the other hand, if it is a response indicating a processing failure, it sets its own state to an error recovery waiting state and confirms this state (error recovery waiting state) to detect that an error has occurred in the device driver 3.

  When the state detection unit 26 detects that an error has occurred in the device driver 3, the return processing unit 27 performs an appropriate return process (for example, an error message) based on the state (error content) of the device driver 3. It functions as a means for sending a command for restoration, etc.).

  The initialization setting request unit 28 functions as a unit for setting the state of the device driver 3 to a state based on the stored initialization setting information when the device driver 3 returns from an error by the return processing unit 27. Thereby, the state of the device driver 3 can be set to the initialization state (the same state as after the initialization processing) without actually performing communication or instance initialization processing.

  Here, with reference to the sequence diagrams of FIGS. 3 to 5, the processing of the controller 2 will be described with a specific example. FIG. 3 is an example of a sequence for explaining the processing of the controller 2 when the application 1 that performs rough error processing is targeted. The rough error process is a process in which, when an error occurs in the device driver 3, the application 1 makes a termination process request and an initialization request regardless of the content of the error and the state of the device driver 3.

  First, the application 1 issues an initialization request for initializing the device driver 3 to the controller 2 (S01). The controller 2 determines whether or not this initialization request is the first initialization request after the application 1 is activated (that is, whether or not it is the first initialization request received from the application 1). Here, since it is the first initialization request, the controller 2 bridges the initialization request to the device driver 3 (S02). Upon receiving the initialization request, the device driver 3 executes initialization processing (communication and instance initialization) based on the initialization request (S03), and a response (hereinafter, “ "Success response" is returned to the controller 2 (S04).

  Subsequently, the controller 2 that has received the success response to the initialization request acquires the current state of the device driver 3, that is, the state immediately after the initialization process, and stores it as initialization setting information (S05). Then, the controller 2 bridges the success response to the initialization request from the device driver 3 to the application 1 (S06).

  Subsequently, the application 1 makes a processing request (processing request A) for causing the device driver 3 to execute the predetermined processing A to the controller 2 (S07). The controller 2 that has received the processing request A checks its own state (normal state or error recovery waiting state). That is, it is confirmed whether or not an error has occurred in the device driver 3. Here, the controller 2 bridges the processing request A to the device driver 3 (S08) because its own state is a normal state (that is, the device driver 3 is operating normally).

  The device driver 3 that has received the processing request A executes processing A based on the processing request A (S09), and returns a success response indicating that the processing A has been successful to the controller 2 (S10). Then, the controller 2 bridges the success response to the processing request A from the device driver 3 to the application 1 (S11).

  Subsequently, the application 1 makes a processing request (processing request B) for causing the device driver 3 to execute the predetermined processing B (S12). The controller 2 that has received the processing request B checks its own state (normal state or waiting for error recovery). Here, the controller 2 bridges the processing request B to the device driver 3 (S13) because its own state is a normal state (that is, the device driver 3 is operating normally).

  Upon receiving the processing request B, the device driver 3 executes processing B based on the processing request B (S14). At this time, if the process B fails, the device driver 3 returns a response indicating that the process B has failed (hereinafter referred to as “failure response”) to the controller 2 (S15). Upon receiving a failure response to the processing request B from the device driver 3, the controller 2 detects that an error has occurred in the device driver 3 using this as a trigger, and changes its own state to an error recovery waiting state (S16). . Then, the controller 2 bridges the failure response to the processing request B to the application 1 (S17).

  Next, the controller 2 confirms the state (error content) of the device driver 3 and executes a return process based on this state (for example, issues a predetermined return command according to the error content of the device driver 3; S18). ).

  Here, when the application 1 that has received the failure response to the processing request B performs a processing request (end processing request) for ending a series of processing to the controller 2 to perform error processing (S19), The controller 2 does not bridge the process end request to the device driver 3, and returns a success response indicating that the end process request is successful to the application 1 (S20).

  Subsequently, when the device driver 3 recovers from the error by the recovery process of S18, the device driver 3 notifies the controller 2 (that has recovered from the error) (error recovery notification) (S21). Upon receiving the error return notification, the controller 2 requests to set the state of the device driver 3 to a state based on the stored initialization setting information (S22). Thereby, the device driver 3 sets its own state to the initialization state (the same state as the state immediately after the initialization process of S03 is executed) (S23). Then, the controller 2 receives a success response indicating that the setting is successful from the device driver 3 (S24), and changes its own state from the error recovery waiting state to the normal state (S25).

  Here, when an initialization request is made from the application 1 as part of error processing (S26), the controller 2 succeeds to the initial request for the application 1 without bridging the initialization request to the device driver 3. A response is returned (S27). That is, even if there is an initialization request from the application 1, the initialization process of the device driver 3 is not actually executed. Then, the application 1 that has received the success response to the initialization request determines that the error processing of the device driver 3 has been completed, and retries the processing request A (S28).

  The controller 2 that has received the processing request A checks its own state (normal state or error recovery waiting state). Here, the controller 2 bridges the processing request A to the device driver 3 because its own state is normal (that is, the device driver 3 has recovered from the error and is operating normally) (S29). . The device driver 3 that has received the processing request A executes the processing A based on the processing request A (S30), and returns a success response indicating that the processing A is successful to the controller 2 (S31). Then, the controller 2 bridges the success response to the processing request A from the device driver 3 to the application 1 (S32). Thereafter, the application 1 makes a processing request (processing request B) following the processing request A.

  As described above, by introducing the controller 2 of the present invention to the application 1 that performs the initialization process (initialization request) regardless of the state of the device driver 3 and the error content as the error process, the application 1 performs the error process. Since the initialization process of the device driver 3 is not performed in response to the initialization request made as described above, the performance of the entire process can be improved.

  Next, FIG. 4 will be described. FIG. 4 is an example of a sequence for explaining the processing of the controller 2 when the application 1 that does not perform error processing is targeted. The sequence in FIG. 4 is different from the sequence in FIG. 3 in that the application 1 does not perform error processing when an error of the device driver 3 occurs and retries a processing request. Hereinafter, different parts will be described.

  When the application 1 receives a failure response to the process request B in the process of S57, the application 1 retries the process request A to the controller 2 (S59). The controller 2 that has received the processing request A checks its own state (normal state or error recovery waiting state) (S60). Here, the controller 2 does not bridge the processing request A to the device driver 3 but to the application 1 because its own state is an error recovery waiting state (that is, an error has occurred in the device driver 3). A failure response of the processing request B is returned (S61).

  That is, the controller 2 bridges the processing request from the application 1 to the device driver 3 until the device driver 3 recovers from the error by the return processing of S58 (while the error occurs in the device driver 3). Instead, a process of returning a failure response to the application 1 is performed. As described above, since the error processing is performed on the controller 2 side, when the processing request fails, it is possible to deal with the application 1 in which the processing request is retried without performing the delicate error processing.

  Next, FIG. 5 will be described. FIG. 5 is an example of a sequence for explaining the process of the controller 2 when the application 1 that initializes the device driver 3 for each fixed process is targeted. Here, an application 1 that repeats this processing set is illustrated as a set of processing that continuously performs processing request A, processing request B, end processing request, and initialization request. Note that the processing from S81 to S86 is the same as the processing from S01 to S06 in FIG.

  After completing the processing from S81 to S86, the application 1 makes a processing request (processing request A) for causing the device driver 3 to execute the predetermined processing A to the controller 2 (S87). The controller 2 that has received the processing request A confirms the state of the device driver 3. Here, since the device driver 3 is operating normally, the controller 2 bridges the processing request A to the device driver 3 (S88). The device driver 3 that has received the processing request A executes the processing A based on the processing request A (S89), and returns a success response indicating that the processing A is successful to the controller 2 (S90). Then, the controller 2 bridges the success response to the processing request A from the device driver 3 to the application 1 (S91).

  Subsequently, the application 1 makes a processing request (processing request B) for causing the device driver 3 to execute the predetermined processing B to the controller 2 (S92). The controller 2 that has received the processing request B checks the state of the device driver 3. Here, since the device driver 3 is operating normally, the controller 2 bridges the processing request B to the device driver 3 (S93). Upon receiving the processing request B, the device driver 3 executes processing B based on the processing request B (S94), and returns a success response indicating that the processing B is successful to the controller 2 (S95). Then, the controller 2 bridges the success response to the processing request B from the device driver 3 to the application 1 (S96).

  Subsequently, when the application 1 makes a process request (end process request) for ending a series of processes to the controller 2 (S97), the controller 2 bridges the process end request to the device driver 3. First, a success response indicating that the termination processing request has been successful is returned to the application 1 (S98). Subsequently, when the application 1 makes an initialization request to the controller 2 (S99), the controller 2 does not bridge the initialization request to the device driver 3, and the initialization request to the application 1 succeeds. A success response indicating this is returned (S100). Thereafter, the application 1 repeats the processing from S87 to S100 (processing in a range surrounded by a one-dot chain line).

  As described above, the controller 2 of the present invention does not bridge the initialization request to the device driver 3 even if the application 1 requests the initialization process for every fixed process (at a predetermined timing). That is, the initialization process of the device driver 3 is not executed. Thereby, the processing performance can be improved by introducing the controller 2 of the present invention to the application 1 that requires the initialization process for every fixed process.

  As described above, according to the present embodiment, when an error occurs in the device driver 3, the controller 2 performs an appropriate return process (error process) according to the state of the device driver 3 (according to the error content). Execute. As a result, the application 1 does not need to perform delicate error processing, so the processing flow of the application 1 can be simplified, and the cost for application development can be reduced.

  In addition, the controller 2 stores the state (initialization setting information) of the device driver 3 after the initial initialization process, and after the device driver 3 recovers from the error, the device driver is based on the initialization setting information. The state 3 can be made equivalent to that after the initialization process. This eliminates the need for initialization processing that requires a long time, such as communication and instance initialization, and improves processing performance.

  The application 1 only needs to perform device control using the first input / output interface 11 provided by the controller 2. For example, the application 1 determines whether the processing has succeeded or failed for each processing request. Sequential processing for determining the next processing request based on the result may be performed, or after a plurality of processing requests are collectively executed, the success / failure of the processing is determined, and the next based on the determination result It is also possible to perform batch processing for determining the processing request.

  As an example of the latter, for example, an application 1 that collectively defines a plurality of processing requests in XML, which is a kind of markup language, and performs batch processing can be considered. Even in the case of the application 1 that cannot perform error processing (error handling) delicately because of batch processing like the application 1, appropriate error processing is performed by introducing the controller 2 of the present invention. Therefore, the application 1 that performs such batch processing can be easily realized.

  The controller 2 of the present embodiment can also be applied to a device driver 3 (UPOS-compliant driver) that realizes specifications conforming to the UPOS (Unified POS) standard. In this case, the input / output interface (second input / output interface 12) between the controller 2 and the UPOS-compliant driver can be realized by an input / output interface compliant with the UPOS specification.

  DESCRIPTION OF SYMBOLS 1 ... Application 2 ... Controller 3 ... Device driver 21 ... Processing request receiving means 22 ... Request processing means 23 ... Response processing means 24 ... Initialization setting information acquisition means 25 ... Initialization setting information storage means 26 ... Status detection means 27 ... Return Processing means 28 ... Initialization setting request means CM ... Component model

The present invention relates a response to the processing request to the control how the controllers of the line Utame.

In view of the above problems, it can simplify the development of applications, and an object thereof to provide a control how the controller can improve the processing performance for controlling the device.

The method of the controller of the present invention is a control method of the row Uco Controller responses to treatment requirements, when receiving a processing request, the received processing request is an initialization request, the initialization request it is determined whether or not the first initialization request, if the received initialization request is determined to be the first initialization request, performs an initialization process, the received initialization request is not the first initialization request If it is discriminated, the initialization process is not performed .

In this case, when it is determined that the received initialization request is not the first initialization request, it is preferable to return a response to the initialization request without performing the initialization process.

In this case, when it is determined that the received initialization request is the first initialization request, after performing the initialization process, the initialization setting information indicating the state after the initialization process is further stored, and the operation state is changed. When detecting that an error has occurred when detecting and detecting the operation state, a recovery process based on the error is executed, and when the error is recovered from the error recovery process, the operation state is stored as initialization setting information. It is preferable to set to a state based on.

Another controller control method of the present invention is a controller control method for responding to a processing request. When a processing request is received and the received processing request is an initialization request, initialization based on the initialization request is performed. Initialization setting information indicating the state after processing is stored, the operation state is detected, and when the operation state is detected, when the occurrence of an error is detected, the return process based on the error is executed, and the return process When returning from the error by the above, the operation state is set to a state based on the stored initialization setting information.

In this case, if an error has been detected and a processing request is received before returning from the error by return processing, a failure response to the processing request is returned without executing processing based on the processing request. Is preferred.

In this case , the processing request is preferably a definition of a plurality of processing requests collectively.

In this case , the plurality of processing requests are preferably defined in a markup language.

Claims (7)

A controller that is a software module that is interposed between an application and a device driver and transfers a processing request from the application to the device driver and a response to the processing request from the device driver to the application. A control method,
A process request receiving step for receiving the process request from the application;
If the received processing request is an initialization request, an initialization request determination step for determining whether the initialization request is the first initialization request after the application is started,
As a result of determination in the initialization request determination step, if the initialization request is the first initialization request, an initialization request transmission step of transmitting the initial initialization request to the device driver;
An initialization setting information storage step for acquiring initialization setting information indicating a state after the initialization process of the device driver based on the initial initialization request from the device driver, and storing the initialization setting information;
A state detection step of detecting a state of the device driver;
In the state detection step, when it is detected that an error has occurred in the device driver, a return processing step for executing a return process based on the state of the device driver;
An initialization setting request step for transmitting, to the device driver, a request for setting the state of the device driver to a state based on the stored initialization setting information when the device driver returns from an error by the return processing; A method for controlling a controller, comprising:   As a result of determination in the initialization request determination step, if the received initialization request is not the first initialization request, the initialization request is not transmitted to the device driver, depending on the state of the device driver, The controller control method according to claim 1, wherein a response to the initialization request is returned to the application. A controller that is a software module that is interposed between an application and a device driver and transfers a processing request from the application to the device driver and a response to the processing request from the device driver to the application. There,
Processing request receiving means for receiving the processing request from the application;
If the received processing request is an initialization request, initialization request determination means for determining whether the initialization request is the first initialization request after the application is started, and
As a result of the determination in the initialization request determination means, if the initialization request is the first initialization request, an initialization request processing means for transmitting the initial initialization request to the device driver;
Initialization setting information acquisition means for acquiring initialization setting information indicating the state after initialization processing of the device driver based on the initial initialization request from the device driver;
Initialization setting information storage means for storing the acquired initialization setting information;
State detection means for detecting the state of the device driver;
In the state detection unit, when it is detected that an error has occurred in the device driver, a return processing unit that executes a return process based on the state of the device driver;
An initialization setting requesting means for transmitting to the device driver a request for setting the state of the device driver to a state based on the stored initialization setting information when the device driver recovers from an error by the return processing; The controller characterized by having. The initialization request processing means includes:
If the received initialization request is not the first initialization request as a result of the determination in the initialization request determination means, the initialization request is not transmitted to the device driver, depending on the state of the device driver, The controller according to claim 3, wherein a response to the initialization request is returned to the application.   The input / output interface of the controller has any one of the same specification as the input / output interface of the device driver and a specification obtained by extending the input / output interface of the device driver. controller.   6. The controller according to claim 3, wherein the processing request is a definition of a plurality of processing requests collectively.   The controller according to claim 6, wherein the plurality of processing requests are defined in a markup language.

Images