JP4342545B2 - Information processing method and information processing system - Google Patents

Description

  The present invention relates to an information processing method and an information processing system including an information processing device and an information processing terminal that uses information provided from the information processing device.

  In recent software development, a client server type system is generally used. In this client-server system, processing condition data or the like is input from an information processing terminal that is a client, and processing is realized by transmitting the input data to an information processing device that is a server. Therefore, in such a client server system, the program executed by the information processing terminal and the program executed by the information processing apparatus must be synchronized. Specifically, for example, when a correction is generated in a program executed by the information processing apparatus, the correction may also occur in a program executed by the information processing terminal.

  For example, in a client server system having a GUI (Graphical User Interface) in an information processing terminal, a result calculated on the information processing apparatus is triggered by an action event by a user operation on a screen displayed on the information processing terminal. In some cases, the information is displayed on the GUI of the information processing terminal (see, for example, Patent Document 1 and Patent Document 2). Here, the action event is an event that occurs when the user operates an input device such as a mouse or a keyboard, and specifically includes pressing of a button, selection from a combo box, input to a text field, and the like.

  Patent Document 1 discloses a Web application server that rapidly and efficiently develops and provides GUI parts to be provided to a client and has excellent maintainability. Patent Document 2 discloses a Web application server system that can reliably acquire user session data with a GUI application server in an environment where processing in one session is executed while moving between a plurality of application servers. Has been.

  When the result calculated on the information processing apparatus is reflected in the GUI of the information processing terminal and displayed, the information processing system 910 includes an information processing terminal 901 that is a client and an information processing apparatus that is a server, as shown in FIG. 903. The information processing terminal 901 includes a GUI container 911. The information processing apparatus 903 includes a J2EE container 931, and the J2EE container 931 includes a business logic execution class 932.

  The GUI container 911 of the information processing terminal 901 includes, for example, a GUI including fields for inputting a zip code and an address, and a user action class 912 that operates the GUI. The user action class 912 receives, from the OS, an action event in which an input signal such as character input or selection is input to a GUI field by a user operation, acquires data input in the field, and processes the information processing apparatus. To 903.

  When the business logic execution class 932 of the information processing apparatus 903 acquires field data from the information processing terminal 901, the business logic is executed based on the acquired data and new field data is transmitted to the information processing terminal 901.

  When the user action class 912 of the information processing terminal 901 receives new field data from the information processing apparatus 903, the user action class 912 reflects the new field data in the field.

  In this case, the module of the information processing terminal that has received the action event is mounted on a different apparatus using technologies such as RPC (Remote Procedure Call), CORBA (Common Object Request Broker Architecture), and RMI (Remote Method Invocation). Functions and methods on the information processing apparatus are called by exchanging messages between objects. Further, the information processing terminal receives a return value of the called function or method from the information processing apparatus, and executes a function or method for controlling the GUI of the information processing terminal based on the received return value.

  However, there are cases where the return values of functions and methods on the information processing apparatus include data that does not need to be reflected in the GUI. At this time, the amount of data transferred from the information processing apparatus to the information processing terminal may increase. In addition, there are methods having iterators and return values of collections such as util.Iterator interface and sql.ResultSet in the Java (registered trademark) language disclosed in Non-Patent Document 1 and the like. In this case, data is acquired one by one from the return value using a loop function or the like.

To solve this problem, create a wrapper method on the information processing device that extracts data from the return value of the method on the existing information processing device, processes it, and returns it as a return value, and then calls it from the information processing terminal There is.
JP 2005-227405 A JP 2005-285007 A http://sdc.sun.co.jp/java/index.html

  However, when many methods on the information processing apparatus already exist and many of them are methods having an iterator, it is necessary to develop a wrapper method for each method, and thus there is a problem that development is not easy.

  To solve such a problem, for example, in an information processing apparatus, without creating a wrapper method for an existing method, a calculation result performed on the information processing apparatus is triggered by an action event that has occurred on the information processing terminal. There is a need for a technology that improves the development efficiency of developers by reflecting them in the GUI of an information processing terminal.

  Accordingly, an object of the present invention is to provide an information processing method for improving development efficiency in an information processing system including an information processing device and an information processing terminal that uses information provided from the information processing device, and information using the information processing method. It is to provide a processing system.

In order to solve the above problems, a first feature of the present invention is an information processing method used in an information processing system including an information processing device and an information processing terminal that uses information provided from the information processing device. . That is, in the information processing method according to the first aspect of the present invention, the information processing terminal displays a GUI screen on the information processing terminal in accordance with an instruction of the information processing device, and generates an input event on the GUI screen; In the information processing apparatus, when an event that an input event has occurred is input, the input event is converted into a user action, and a thread for executing the user action in the GUI object stub that is a GUI object stub corresponding to the input event is generated. is Rutotomoni acquires the GUI thread ID, the request agent unit of the information processing terminal, and transmitting the address and the GUI thread ID of the business logic execution unit for executing the business logic, the request agent unit of the information processing terminal , Business logic execution section address and When receiving the GUI thread ID, based on the received address and GUI thread ID, call the business logic execution unit of the information processing apparatus, and executing the user action, the information processing apparatus, the GUI objects in the execution of a user action When the method is called, a new GUI screen is displayed on the information processing terminal based on the parameters related to the call, a step of generating a new input event for the new GUI screen, and a new input in the information processing device When an event occurrence is input, a new input event is converted into return data, and the result of executing the user action in the thread based on the return data is output as the return value of the user action execution instruction. the method comprising the steps of: Provided.

  In the information processing method according to the first feature of the present invention, the GUI operation method and the business logic are executed by the information processing apparatus only by displaying the GUI screen on the information processing terminal and receiving the input event. It is possible to provide an information processing method that reduces the amount of development work on the information processing terminal side and improves development efficiency.

A second feature of the present invention is an information processing method used in an information processing system including an information processing apparatus and an information processing terminal that uses information provided from the information processing apparatus. That is, the information processing method according to the second feature of the present invention includes the step of storing the GUI object and the GUI object ID for identifying the GUI object in association with each other in the GUI object management unit of the GUI execution unit of the information processing apparatus; In the action management unit of the business logic execution unit of the information processing apparatus, a step of associating and storing a user action that occurs in the GUI object and an action ID that identifies the user action, and a GUI of the business logic execution unit of the information processing apparatus In the stub management unit, the GUI object ID and a GUI object stub that is a stub of the GUI object associated with the GUI object ID are stored in association with each other, and the GUI execution unit of the information processing apparatus performs the GUI object A GUI screen is displayed on the information processing terminal based on the project, and when an input event occurs on the GUI screen, the step of transmitting the input event to the GUI execution unit of the information processing device, and the GUI execution unit of the information processing device, When an input event is received, a GUI operation method is executed based on the input event to generate a user action event, and an action ID and a GUI object related to the user action are acquired. A thread for executing a user action is generated, an action count variable is initialized, a GUI thread ID is acquired, and in the GUI execution unit of the information processing apparatus, the address of the business logic execution unit and the GUI thread ID are Processing terminal request A step of transmitting to the processing unit, a step of calling a business logic execution unit of the information processing device based on the address and the GUI thread ID in the request proxy unit of the information processing terminal, and a GUI thread in the GUI execution unit of the information processing device When the ID, the action ID, and the GUI object are acquired, the GUI object ID is acquired from the GUI object management unit based on the GUI object, and an action call packet including the action ID and the GUI object ID is generated. The GUI execution unit of the apparatus increments the action count variable and transmits an action call packet to the business logic execution unit of the information processing apparatus, and the business logic of the information processing apparatus. In click execution unit, upon receiving the action call packet, it obtains the action ID and the GUI object ID from the action call packet, acquires the user action from action manager based on the action ID, GUI stub based on the GUI object ID A step of acquiring a GUI object stub from the management unit, and a step of executing the acquired user action on the acquired GUI object stub in the business logic execution unit of the information processing apparatus.

Here, in the business logic execution unit of the information processing apparatus, when a method of the GUI object stub is called from the user action with a predetermined parameter, a method call packet including the GUI object ID and the parameter is generated, and the GUI execution unit When the method execution packet is received in the transmission step and the GUI execution unit of the information processing apparatus, the GUI object ID and the parameter are extracted from the method call packet, and the GUI object is acquired from the GUI object management unit based on the GUI object ID. The GUI execution unit of the information processing apparatus displays a new GUI screen on the information processing terminal based on the acquired GUI object and parameter, and a new input event is generated on the new GUI screen. When it is generated , a new input event is transmitted to the GUI execution unit of the information processing device and converted into GUI object return data, and a method return packet including the GUI object return data is generated in the GUI execution unit of the information processing device. and sending the business logic execution unit of the information processing apparatus, the business logic execution unit of the information processing apparatus receives the method return packet, obtains the GUI object return data from method return packet, a GUI object returns data it may further comprise the step of returning the method's return the GUI object's stub.

Furthermore, in the business logic execution unit of the information processing apparatus, when the action return data is acquired as the return value of the method of the GUI object stub, an action return packet including the action return data is created, and the action return packet is received. A step of returning as a return value and a step of decrementing the action count variable when the action return packet is received in the GUI execution unit of the information processing device, and acquiring action return data from the action return packet when the action count variable becomes zero And may further be provided.

A third feature of the present invention is an information processing system including an information processing device and an information processing terminal that uses information provided from the information processing device. That is, the information processing terminal of the information processing system according to the third feature of the present invention displays a GUI screen on the display device of the information processing terminal according to the instruction of the information processing device, When the address and GUI thread ID of the business logic execution unit that executes business logic in the information processing apparatus are received from the information processing apparatus, the received address and GUI thread ID are transmitted to the information processing apparatus. Based on the above, the business logic execution unit of the information processing apparatus is called. The information processing apparatus of the information processing system according to the third aspect of the present invention outputs a command to display a GUI screen on the information processing terminal, and converts an input event into a user action when an input event occurs on the GUI screen. The address of the business logic execution unit and the GUI thread ID are transmitted to the request proxy unit of the information processing terminal, and the business logic execution unit responds to the input event in response to the call from the request proxy unit of the information processing terminal. When a thread for executing a user action is generated in the GUI object stub, which is a GUI object stub corresponding to the GUI screen, the user action is executed in the thread, and when the method of the GUI object is called in the execution of the user action, Based on parameters When a command to display a new GUI screen is output to the information processing terminal and a new input event occurs on the new GUI screen, the new input event is converted into return data, and in the thread based on the return data The result of executing the user action is output as the return value of the user action execution instruction.

  In the information processing system according to the third feature of the present invention, the GUI operation method and the business logic are executed by the information processing apparatus only by displaying the GUI screen and receiving the input event at the information processing terminal. It is possible to provide an information processing method that reduces the amount of development work on the information processing terminal side and improves development efficiency.

  According to the present invention, an information processing method for improving development efficiency in an information processing system including an information processing device and an information processing terminal that uses information provided from the information processing device, and information processing using the information processing method A system can be provided.

  Next, embodiments of the present invention will be described with reference to the drawings. In the following description of the drawings, the same or similar parts are denoted by the same or similar reference numerals.

  In the best mode of the present invention, the sequence diagrams of FIGS. 2, 9 and 10 are described in accordance with UML (Unified Modeling Language). Specifically, when the method call from the A object to the B object is a synchronous message, the synchronous message is represented by a solid line arrow filled with a triangle like S101 in FIG. Also, the return value for this method call is represented by a dotted arrow as in S127 of FIG. On the other hand, when the method call from the A object to the B object is an asynchronous message, it is represented by a solid line arrow as in S104 of FIG. Here, the asynchronous message is a message in which the called process is performed without waiting for the caller to complete the process.

(Best Embodiment)
(Information processing system)
With reference to FIG. 1, an outline of an information processing system 4 according to the preferred embodiment of the present invention will be described. An information processing system 4 according to the best mode of the present invention includes an information processing terminal 1 as a client and an information processing apparatus 2 as a server. The information processing terminal 1 includes a GUI container, and the information processing apparatus 2 includes a J2EE container including a remote user action class that controls the GUI of the information processing terminal 1.

  In the information processing terminal 1, when an input event for the field of the GUI container occurs due to the operation of the input device by the user, the information processing device 2 receives the input event from the information processing terminal 1 and acquires the field data of the GUI container. . Furthermore, the information processing apparatus 2 has a stub for the GUI object of the information processing terminal 1, executes business logic based on the field data acquired using the stub, and obtains a new field obtained as a result. Data is set in the information processing terminal 1.

  As described above, in the information processing system 4 according to the preferred embodiment of the present invention, the stub method of the GUI object on the server is executed using the input event generated in the GUI object on the information processing terminal 1 as a trigger. Thus, the user action can be executed by the information processing apparatus 2 and the data of the return value can be reflected in the GUI object of the information processing terminal 1.

  Next, referring to FIG. 2, in the information processing system 4 according to the preferred embodiment of the present invention, an action event is generated for the GUI of the information processing terminal 1, and as a return value for the generated action event, A case where a command for executing a GUI object is newly acquired will be described. In FIG. 2, the GUI object unit 21, the action management unit 34, and the GUI stub management unit 33 are included in the information processing apparatus 2. The GUI object unit 21 manages a GUI object displayed on the information processing terminal 1, receives an input event from the information processing terminal 1, transmits the processing result to the information processing terminal 1, displays the screen, and inputs An object that converts events into action events. The action management unit 34 is an object in which a user action received by the GUI object unit 21 is associated with an action ID for identifying the user action. The GUI stub management unit 33 is an object in which a GUI object ID that identifies a GUI object managed by the GUI object unit 21 is associated with a GUI object stub that is a stub of the GUI object.

  First, in the information processing terminal 1, a GUI screen is displayed on the information processing terminal 1 in accordance with a command from the information processing apparatus 2, and an input event is generated on the GUI screen.

  Next, when an input event is received from the input unit 12 of the information processing terminal 1 in the GUI object unit 21 of the information processing apparatus 2 in step S1, the input event is converted into an action event and the method of the action management unit 34 is performed. Is called.

  In step S <b> 2, the action management unit 34 calls the GUI stub management unit 33 for the stub method of the GUI object in which the action event has occurred. When the stub method is called, the GUI stub management unit 33 executes the stub method. At this time, the stub method is executed based on the action event received from the GUI object unit 21.

  When a command for newly executing a GUI object is acquired as a return value of this stub method, the GUI stub management unit 33 calls a method of the GUI object with respect to the GUI object unit 21 in step S3. When a method is called from the GUI stub management unit 33, the GUI object unit 21 executes the method in the GUI object unit 21 to display the GUI screen on the screen display unit 11 of the information processing terminal 1 and from the input unit 12. Get input event of. The GUI object unit 21 executes the GUI object based on the input event to generate return data, and transmits the return data to the GUI stub management unit 33 in step S4 as a return value of the GUI object method call in step S3.

  When return data, which is a result of newly executing a GUI object, is transmitted from the GUI object unit 21, the GUI stub management unit 33 executes processing based on the return data. When an instruction to execute a new GUI object is acquired as a return value of the processing, the GUI object method is called again with respect to the GUI object unit 21. On the other hand, if the return value does not include an instruction to execute a new GUI object, in step S5, the return value in the GUI stub management unit 33 is sent to the action management unit 34 as the return value of the stub method call in step S2. return. When the action management unit 34 receives the return data of the stub method call from the GUI stub management unit 33, the action management unit 34 transmits the received data to the GUI object unit 21 as a return value for the action execution in step S1. The GUI object unit 21 displays the received data on the screen display unit 11 of the information processing terminal 1.

  Next, the information processing system 10 according to the preferred embodiment of the present invention will be described in detail with reference to FIG.

  An information processing system 4 according to the best mode of the present invention includes an information processing terminal 1 that is a client and an information processing device 2 that is a server. The information processing terminal 1 and the information processing device 2 are connected via a communication network 5. Are connected to each other. The communication network 5 is a network capable of mutual communication such as the Internet or a LAN.

  As shown in FIG. 4, the information processing apparatus 2 according to the preferred embodiment of the present invention includes a central processing control device 101, a ROM (Read Only Memory) 102, a RAM (Random Access Memory) 103, and an input / output interface 109. Are connected via a bus 110. An input device 104, a display device 105, a communication control device 106, a storage device 107, and a removable disk 108 are connected to the input / output interface 109.

  The central processing control device 101 reads out and executes a boot program for starting up the information processing device 2 from the ROM 102 based on an input signal from the input device 104, and further reads out an operating system stored in the storage device 107. Further, the central processing control device 101 controls various devices based on input signals from the input device 104, the communication control device 106, etc., and reads programs and data stored in the RAM 103, the storage device 107, etc. into the RAM 103. A processing device that loads and implements a series of processes to be described later, such as data calculation or processing, based on a program command read from the RAM 103.

  The input device 104 includes input devices such as a keyboard and a mouse through which an operator inputs various operations. The input device 104 generates an input signal based on the operation of the operator, and inputs via the input / output interface 109 and the bus 110. It is transmitted to the central processing control apparatus 101. The display device 105 is a CRT (Cathode Ray Tube) display, a liquid crystal display, or the like. The display device 105 receives an output signal to be displayed on the display device 105 from the central processing control device 101 via the bus 110 and the input / output interface 109. It is a device that displays the processing result of the control device 101 and the like. The communication control device 106 is a device such as a LAN card or a modem, and is a device that connects the information processing device 2 to a communication network such as the Internet or a LAN. Data transmitted / received to / from the communication network via the communication control device 106 is transmitted / received to / from the central processing control device 101 via the input / output interface 109 and the bus 110 as an input signal or an output signal.

  The storage device 107 is a semiconductor storage device or a magnetic disk device, and stores programs and data executed by the central processing control device 101. The removable disk 108 is an optical disk or a flexible disk, and signals read / written by the disk drive are transmitted / received to / from the central processing control apparatus 101 via the input / output interface 109 and the bus 110.

  A server information processing program is stored in the storage device 107 of the information processing device 2 according to the preferred embodiment of the present invention, and the server information processing program is read and executed by the central processing control device 101 of the information processing device 2. Thus, the GUI execution module (GUI execution unit) 20 and the business logic execution module (business logic execution unit) 30 are mounted on the information processing apparatus 2. The GUI execution module 20 includes a GUI object unit 21, a GUI method execution unit 22, a GUI object management unit 23, an action event reception unit 24, a GUI action execution unit 25, and a communication object management unit 26. The business logic execution module 30 includes an action thread unit 31, a stub method execution unit 32, a GUI stub management unit 33, an action management unit 34, an action execution unit 35, and a business logic thread management unit 36. Data stored in each part of the GUI execution module 20 and the business logic execution module 30 and work data generated when the method is executed are stored in the storage device 107.

  The information processing terminal 1 also has the same hardware configuration as the information processing apparatus 2. A client information processing program is stored in the storage device of the information processing terminal 1, and the GUI display module 10 is read by the central processing control device of the information processing terminal 1 to be executed by the GUI display module 10. To be implemented. The GUI display module 10 includes a screen display unit 11, an input unit 12, and a request proxy unit 13. Data stored in each part of the GUI display module 10 and work data generated when the method is executed are stored in the storage device of the information processing terminal 1.

(Information processing terminal)
With reference to FIG.3 and FIG.5, the information processing terminal 1 which concerns on the best embodiment of this invention is explained in full detail.

  The information processing terminal 1 includes a GUI display module 10. The GUI display module 10 includes a screen display unit 11, an input unit 12, and a request proxy unit 13.

  The screen display unit 11 displays a GUI screen on the display device in accordance with a command from the GUI object unit 21 of the information processing apparatus 1. The input unit 12 transmits an input event from the input device to the GUI object unit 21 of the information processing device 1.

  The request proxy unit 13 includes a post method as shown in FIG. The post method sets a business logic execution module address and a GUI thread ID as arguments, and performs a process of calling “run” of the action thread unit 31 of the information processing apparatus 2. The request proxy unit 13 calls the business logic of the business logic execution module 30 of the information processing device 2 in response to a call from the action event reception unit 24 of the GUI execution module 20 of the information processing device 2. With this operation, it is possible to cope with a case where the business logic responds only to a call from a specific terminal in the case of SSL authentication or the like.

(Information processing device)
The information processing apparatus 2 according to the best embodiment of the present invention includes a GUI execution module (GUI execution unit) 20 and a business logic execution module (business logic execution unit) 30.

  With reference to FIG. 3 and FIG. 6, the GUI execution module 20 of the information processing apparatus 2 according to the preferred embodiment of the present invention will be described in detail.

  The GUI execution module 20 includes a GUI object unit 21, a GUI method execution unit 22, a GUI object management unit 23, an action event reception unit 24, a GUI action execution unit 25, and a communication object management unit 26.

  As shown in FIG. 6A, the GUI object unit 21 has a GUI object that is a GUI component, and a GUI operation method capable of operating the GUI object. Further, the GUI object unit 21 outputs a command to display the GUI screen on the screen display unit 11 of the information processing terminal 1, receives an input event from the input unit 12 of the information processing terminal 1, and based on the received input event The GUI operation method is executed to generate an action event, and the action ID and GUI object are input to the action event receiving unit 24.

  As shown in FIG. 6B, the GUI method execution unit 22 includes an invoke method. The invoke method is called with a MethodCall packet (method call packet) set as an argument, and calls the GUI operation method of the GUI object.

  The GUI object management unit 23 manages a GUI object and a GUI object ID as a pair. As shown in FIG. 6C, the GUI object management unit 23 includes a getObjectID method and a getObject method. The getObjectID method retrieves a GUI object ID from the GUI object and returns a GUI object ID as a return value. The getObject method searches for a GUI object from the GUI object ID, and returns a GUI object as a return value.

  The action event receiving unit 24 includes a receiveEvent method as shown in FIG. The receiveEvent method is called from the GUI object unit 21 with an action ID and a GUI object set as arguments. The receiveEvent method generates the communication object management unit 26, calls the start method of the communication object management unit 26, and returns action return data as a return value to the GUI object unit 21. Furthermore, the receiveEvent method generates a GUI action execution unit 25 and calls runAction of the GUI action execution unit 25.

  The GUI action execution unit 25 performs initial processing for sending an action event to the action execution unit 35 as a final destination. The GUI action execution unit 25 includes a runAction method as shown in FIG. The runAction method is called with a GUI thread ID, action ID, and GUI object set, and returns action return data as a return value. The ruAction method of the GUI action execution unit 25 generates an ActionCall packet (action call packet), calls the exchangePacket method of the communication object management unit 26, and receives the received packet as a return value. If the received packet is an ActionReturn packet, the runAction method returns action return data. On the other hand, if the received packet is a MethodCall packet (method call packet), the runAction method calls the invoke method of the GUI method execution unit 22 and passes the return value to the argument of the exchangePacket method of the communication object management unit 26 again.

  As shown in FIG. 6 (f), the communication object management unit 26 uses a GUI thread ID as a key, and records a pair of an integer with an initial value 0 of ACTION_COUNT (action count variable) and an initial value FALSE flag INIT. Is provided. The GUI thread ID includes an address that uniquely represents the GUI execution module and an ID that uniquely represents the GUI thread ID. The communication object management unit 26 includes a getGuiThreadID method, an isNewThread method, a start method, and an exchangePacket method. The getGuiThreadID method acquires the GUI thread ID and returns it as a return value. The start method is a thread that adds a record with the GUI thread ID as a key to the communication object management unit 26 and executes a user action. The isNewThread method sets a GUI thread ID as an argument, and returns FALSE as a return value if there is a record using the GUI thread ID as a key.

  In the exchangePacket method, a GUI thread ID and a packet are set as arguments. Packets are exchanged between two threads according to the flowchart of FIG. When receiving an action return packet as an argument of the exchangePacket method called from the A thread, the communication object management unit 26 returns an action return packet as a return value of the exchangePacket method called from the B thread, and decrements the action count variable. When the action count becomes 0, the communication object management unit 26 returns null as a return value of the exchangePacket method called from the A thread. In other cases, when the exchangePacket method is called from the A thread with the A packet as an argument, the communication object management unit 26 returns the A packet as a return value of the exchangePacket previously called from the B thread and is called from the A thread. The received exchangePacket method waits.

  Here, the packet handled by the communication object management unit 26 has a class configuration as shown in FIG. The packet includes a transmission packet and a reception packet. The transmission packet includes a client thread ID, and includes a thread start packet, an action call packet including an action ID and a GUI object ID, and a method return packet including GUI object return data. The received packet includes a method call packet including a GUI object ID and a parameter, and an action return packet including an action return packet.

  Next, the business logic execution module 30 of the information processing apparatus 2 according to the preferred embodiment of the present invention will be described in detail with reference to FIG. 3 and FIG.

  The business logic execution module 30 includes an action thread unit 31, a stub method execution unit 32, a GUI stub management unit 33, an action management unit 34, an action execution unit 35, and a business logic thread management unit 36.

  The action thread unit 31 includes a run method as shown in FIG. The run method is called with a GUI thread ID set as an argument. The run method receives an ActionCall packet for executing an action by using the exchangePacket method of the communication object management unit 26, generates an action execution unit 35, calls the invokeAction of the action execution unit 35, and returns the return value again. Passed to the communication object management unit 26 as an argument of the exchangePacket method.

  As shown in FIG. 8B, the stub method execution unit 32 includes an invokeMethod method. The invokeMethod method is called with a GUI object ID and parameters set. The invokeMethod method passes a MethodCall packet by the exchangePacket method of the communication object management unit 26 in accordance with the GUI stub call. When the MethodReturn packet is returned as the return value of the exchangePacket method, the invokeMethod method returns GUI object return data as the return value of the GUI stub. When the ActionCall packet is returned, the invokeMethod method newly creates the action execution unit 35, calls the invokeAction of the action execution unit 35, and passes the return value again as an argument of the exchangePacket of the communication object management unit 26. The invokeMethod method repeats the same processing until a MethodReturn packet is returned as the return value of exchangePacket.

  The GUI stub management unit 33 manages the GUI stub and includes a getObjectStub method as shown in FIG. The getObjectStub method is called with an object ID set as an argument, generates a GUI object stub based on the object ID, and returns a GUI object stub as a return value. Here, the GUI object stub corresponds to the GUI object ID as shown in FIG.

  The action management unit 34 manages user actions and includes a getAction method as shown in FIG. The getAction method is called with an action ID set as an argument, searches for a user action based on the action ID, and returns a user action as a return value.

  The action execution unit 35 includes an invokeAction method as shown in FIG. The invokeAction method is called by setting an ActionCall packet as an argument, acquires a user action from the action management unit 34, and calls the user action using the GUI object stub acquired from the GUI stub management unit 33 as an argument.

  The business logic thread management unit 36 has three methods: a setGuiThreadID method, a getGuiThreadID method, and a removeGuiThreadID method. The setGuiThreadID method is called with a GUI thread ID set as an argument, acquires a business logic thread ID using a thread ID acquisition unit, and stores a pair of GUI thread ID and business logic thread ID as one record. The getGuiThreadID method acquires a business logic thread ID using a thread ID acquisition unit, searches for a GUI thread ID using the business logic thread ID as a key, and returns a GUI thread ID. The removeGuiThreadID method is called with a GUI thread ID set as an argument, searches for a record using the GUI thread ID as a key, and deletes the searched record.

(Information processing method)
Next, an information processing method according to the best embodiment of the present invention will be described with reference to FIGS.

  First, with reference to FIG. 9, a process until a user action is executed will be described.

  When the GUI object unit 21 receives an input event from the input unit 12 of the GUI display module 10 of the information processing terminal 1, the GUI object unit 21 acquires an action ID and a GUI object related to the user action from the input event. In step S101, the GUI object unit 21 calls the receiveEvent method of the action event reception unit 24 with an action ID and a GUI object as arguments.

  When the receiveEvent method is called from the GUI object unit 21, in step S102, the action event receiving unit 24 calls the getGuiThreadID method of the communication object management unit 26 without setting an argument in the receiveEvent method, and returns a GUI thread ID as a return value. To get. Furthermore, the action event reception unit 24 calls the isNewThread method of the communication object management unit 26 with the GUI thread ID set as an argument. The action event reception unit 24 obtains a Boolean value TRUE as a return value, and confirms that a record having the GUI thread ID as a key exists in the communication object management unit 26. After acquiring the Boolean value TRUE, the action event receiving unit 24 calls the start method of the communication object management unit 26 with the GUI thread ID as an argument.

  In the start method, the communication object management unit 26 creates a record in which ACTION_COUNT and INIT are associated with the GUI thread ID to initialize each variable. In step S103, the communication object management unit 26 sets the GUI thread ID as a response to step S102. Return to the event receiver.

  In the receiveEvent method, the action event receiving unit 24 asynchronously calls the post of the request proxy unit 13 of the information processing terminal 1 by setting the business logic execution module address and the GUI thread ID as arguments in step S104.

  When the post method is called, the request proxy unit 13 of the information processing terminal 1 searches for the business logic execution module 30 based on the business logic execution module address that is an argument in the post method. In step S105, the action thread unit The 31 run method is called with the GUI thread ID set as an argument.

  In the run method, the action thread unit 31 calls the setGuiThreadID method of the business logic thread management unit 36 by setting the GUI thread ID as an argument, and obtains a response. At this time, the setGuiThreadID method of the business logic thread management unit 36 acquires the business logic thread ID using the thread ID acquisition means, and stores the GUI thread ID and the business logic thread ID as one record in association with each other.

  When the action thread unit 31 obtains a response of the setGuiThreadID method of the business logic thread management unit 36 in the run method, in step S107, the action thread unit 31 searches the communication object management unit 26 based on the address part of the GUI thread ID. The exchangePacket method of the communication object management unit 26 is called with the GUI thread ID and null set as arguments. Further, the communication object management unit 26 sets the variable ACTION_COUNT to 0 in the exchangePacket method and waits.

  On the other hand, in step S106, the action event receiving unit 24 generates the GUI action execution unit 25 in the receiveEvent method, sets the runAction method of the GUI action execution unit 25, and sets the GUI thread ID, action ID, and GUI object as arguments. Then call.

  In the runAction method, the GUI action execution unit 25 calls the getObjectID method of the GUI object management unit 23 by setting the GUI object as an argument, and acquires the GUI object ID as a return value. Further, the GUI action execution unit 25 generates an ActionCall packet including a GUI thread ID, an action ID, and a GUI object ID. In step S108, the exchange packet method of the communication object management unit 26 is used as an argument with the GUI thread ID and the ActionCall packet. Set and call.

  When the GUI thread ID and the ActionCall packet are passed as arguments in the exchangePacket method, the communication object management unit 26 increments the variable ACTION_COUNT by one, and in Step S109, sets the ActionCall packet as the return value of the call from Step S107. It is passed to the action thread unit 31.

  When the action thread unit 31 receives an ActionCalll packet as a return value of the exchangePacket method in the run method, the action thread unit 31 generates an action execution unit 35. In step S110, the action call unit 31 uses the invokeAction method of the action execution unit 35 as an argument. Set and call.

  The action execution unit 35 acquires the action ID and GUI object ID from the ActionCall packet in the invokeAction method, calls the getAction method of the action management unit 34 with the action ID set as an argument, and acquires the user action. Furthermore, the action execution unit 35 acquires the GUI stub by calling the getObjectStub method of the GUI stub management unit 33 with the GUI object ID set as an argument in the invokeAction method. Here, the action execution unit 35 executes a user action using a GUI stub in the invokeAction method.

  With reference to FIG. 9, a process for operating a GUI object from within a user action will be described.

  When the GUI stub method is called from the user action being executed in the invokeAction method of the action execution unit 35, the GUI stub, in step S111, uses the invokeMethod method of the stub method execution unit 32 as a parameter with the GUI object ID and parameters. Set and call. Here, the “parameter” is a parameter used for a method called from the user action being executed.

  The stub method execution unit 32 calls the getGuiThreadID method of the business logic thread management unit 36 in the invokeMethod method without setting an argument, and acquires the GUI thread ID as a return value. Further, the stub method execution unit 32 creates a MethodCall packet including a GUI object ID and parameters in the invokeMethod method, and searches the communication object management unit 26 based on the address portion of the GUI thread ID. In step S112, the stub method execution unit 32 calls the exchangePacket method of the communication object management unit 26 by setting the GUI thread ID and the MethodCall packet as arguments.

  In step S113, the communication object management unit 26 passes the MethodCall packet passed in step S112 to the GUI action execution unit 25 as a return value of the call in step S108 in the exchangePacket method.

  The GUI action execution unit 25 generates the GUI method execution unit 22 in the runAction method, and calls the invoke method by setting a MethodCall packet as an argument in step S114.

  The GUI method execution unit 22 extracts the GUI object ID and parameters from the MethodCall packet in the invoke method. The GUI method execution unit 22 calls the getObject method of the GUI object management unit 23 in the invoke method, setting the GUI object ID as an argument, and acquires the GUI object. In the invoke method, the GUI method execution unit 22 calls the GUI operation method of the GUI object by setting parameters as arguments in step S115.

  The GUI object unit 21 displays on the screen display unit 11 of the information processing terminal 1 based on parameters set as arguments in the GUI operation method, and when GUI object return data is input from the information processing terminal 1. In step S116, the input is passed to the GUI method execution unit 22 as a return value in step S114.

  When the GUI object exists in the GUI object return data in the invoke method, the GUI method execution unit 22 calls the getObjectID method of the GUI object management unit 23 and rewrites the GUI object in the GUI object return data with the GUI object ID. . Further, the GUI method execution unit 22 creates a MethodReturn packet including the GUI thread ID and GUI object return data in the invoke method, and passes the MethodReturn packet to the GUI action execution unit 25 as the return value of step S114 in step S117. Then disappear.

  When the GUI action execution unit 25 acquires the MethodReturn packet in the runAction method, in step S118, the GUI action execution unit 25 calls the exchangePacket method of the communication object management unit 26 with the GUI thread ID and the MethodReturn packet as arguments.

  In step S119, the communication object management unit 26 passes the MethodReturn packet to the stub method execution unit 32 as the return value of step S112 in the exchangePacket method.

  When the MethodReturn packet is acquired as the return value of the exchangePacket method in the invokeMethod method, the stub method execution unit 32 extracts GUI object return data from the MethodReturn packet. When the GUI object return data includes the GUI object ID in the invokeMethod method, the stub method execution unit 32 calls the getObjectStub method of the GUI stub management unit 33 and acquires the GUI stub corresponding to the GUI object ID. The GUI object ID of the GUI object return data is rewritten to a GUI stub. In the invokeMethod method, the stub method executing unit 32 disappears after passing the GUI object return data to the action executing unit 35 as the return value of the GUI stub method call in Step S111 in Step S120.

  Furthermore, user action return processing will be described with reference to FIG.

  When the action execution unit 35 acquires the GUI object return data as the action return data in the invokeAction method, the action execution unit 35 creates an ActionReturn packet including the action return data. In step S121, the action execution unit 35 sends the ActionReturn packet to the action thread unit 31 as the return value. After passing the packet, it disappears.

  The action thread unit 31 receives the ActionReturn packet in the run method, and calls the exchangePacket method of the communication object management unit 26 with the ActionReturn packet as an argument in step S122.

  When the ActionReturn packet is passed in the exchangePacket method, the communication object management unit 26 passes the ActionReturn packet to the GUI action execution unit 25 as a return value of Step S118 in Step S123. The communication object management unit 26 decrements one from the variable ACTION_COUNT in the exchangePacket method. As a result, ACTION_COUNT becomes 0, so the record corresponding to the GUI thread ID is deleted, and null is passed to the action thread unit 31 as the return value of step S122 in step S125.

  In step S126, the action thread unit 31 calls the removeGuiThreadID method of the business logic thread management unit 36 with the GUI thread ID set as an argument, and returns the return of step S105 to the request proxy unit 13. Disappear.

  When the action return packet is received in the runAction method, the GUI action execution unit 25 acquires the action return data from the ActionReturn packet. In step S124, the GUI action execution unit 25 sends the action return data to the action event reception unit 24 as the return value of step S106. hand over.

  The action event receiving unit 24 passes action return data to the GUI object unit 21 as a return value of step S101 in step S127 in the receiveEvent method. The GUI object unit 21 causes the screen display unit 11 of the information processing terminal 1 to display a screen according to the action return data.

  Next, with reference to FIG. 10, a case where an action event occurs from the method of the GUI object called from the business logic execution module 30 will be described.

  Through the processing from step S201 to step S215, the GUI operation method of the GUI object unit 21 is called from the business logic execution module 30.

  The GUI object unit 21 displays on the screen display unit 11 of the information processing terminal 1 based on parameters set as arguments in the GUI operation method. When GUI object return data is input from the information processing terminal 1 and an action event occurs in the GUI object return data, the GUI operation method of the GUI object unit 21 is the receiveEvent method of the action event receiving unit 24 in step S201 ′. Are set with the action ID and GUI object as arguments.

  The action event reception unit 24 calls the getGuiThreadID method of the communication object management unit 26 in the receiveEvent method without setting an argument, and acquires the GUI thread ID as a return value. The action event reception unit 24 calls the isNewThread method of the communication object management unit 26 in the receiveEvent method, calls the GUI thread ID as an argument, and acquires the Boolean value FALSE as a return value. Further, in step S206 ', the action event reception unit 24 creates a GUI action execution unit 25' in the receiveEvent method, and calls the runAction method with the GUI thread ID, action ID, and GUI object as arguments.

  In the runAction method, the GUI action execution unit 25 ′ calls the getObjectID method of the GUI object management unit 23 by setting a GUI object as an argument, and acquires a GUI object ID as a return value. Further, the GUI action execution unit 25 ′ creates an ActionCall packet including a GUI thread ID, an action ID, and a GUI object ID in the runAction method. In step S208 ′, the exchangePacket method of the communication object management unit 26 is set as an argument. And set the GUI thread ID and ActionCall packet.

  When the GUI thread ID and the ActionCall packet are sent as arguments in the exchangePacket method, the communication object management unit 26 increments the variable ACTION_COUNT by one, and in Step S209 ′, the ActionCall as the return value of the call in Step S212. Pass the packet to the stub method 32.

  Since the stub method 32 acquires an ActionCall packet as a return value of the exchangePacket method in the invokeMethod method, the stub method 32 generates an action execution unit 35 ′. In step S210 ′, the invokeAction method of the action execution unit 35 ′ is used as an argument. Set the ActionCall packet and call it.

  With the process shown in FIG. 10, an action can be executed even when an action event occurs from the method of the GUI object called from the business logic execution module 30.

  With reference to FIG. 11, the process of the start method of the communication object management unit 26 according to the preferred embodiment of the present invention will be described. Here, the operation of the communication object management unit 26 in each step of FIGS. 9 and 10 will be described.

(1) Start of processing (step S102 in FIG. 9)
In step S301, the start method of the communication object management unit 26 is started by calling the GUI object unit 21 with the GUI thread ID and packet set as arguments.

(2) Processing in Step S107 in FIG. 9 A case will be described in which, in step S107 in FIG. 9, the exchange thread method is called from the action thread unit 31 with the GUI thread ID and null set as arguments.
In step S302, since the argument packet is determined to be null, the process proceeds to step S303. In step S303, TRUE is substituted into the INIT area. Also, if the call at step S108 in FIG. 9 is earlier, the call thread at step S108 in FIG. 9 is WAITing (waiting) at step S305, so Notify (notify) the waiting call thread at step S108. . In step S313, if the call in step S108 in FIG. 9 is slower, the process waits for the calling thread in step S108 to notify in step S312.
If Notify is made in step S312, the process proceeds to step S314.
In step S314, the packet in the packet area is stored in the stack variable TMP. Here, since the ActionCall packet is stored in Step S312 when calling in Step S108 of FIG. 9, the ActionCall packet is stored in the stack variable TMP. Furthermore, null is assigned to the packet area of the record, and the process proceeds to step S315. In step S315, TMP is returned as a return value.
With this control, after the ActionCall packet received in step S108 is transmitted as the return value in step S107, the return value in step S108 is processed.

(3) Processing in Step S108 in FIG. 9 A case where the GUI action execution unit 25 sets the GUI thread ID and the ActionCall packet as arguments and calls the exchangePacket method in step S108 in FIG. 9 will be described.
In step S302, since it is determined that the argument packet is not null, the process proceeds to step S304. In step S304, if the call of step S107 is earlier, since INIT is already TRUE, the process proceeds to step S306. If the call of step S107 is slower, the process proceeds to step S305.
In step S305, the process waits for Notify from the calling thread in step S107 in step S303, and proceeds to step S306 when notified from the calling thread in step S107.
In step S306, it is determined that the argument is not an ActionReturn packet, and the process proceeds to step S308. In step S308, the argument is determined to be an ActionCall packet, and the process proceeds to step S310. In step S310, ACTION_COUNT is incremented by one, ACTION_COUNT becomes “1”, and the process proceeds to step S312. In step S312, the ActionCall packet is stored in the packet area of the record, and the process advances to step S313 after notifying the calling thread in step S107 of FIG. 9 that is waiting in step S313.
In step S313, in step S312, it waits for Notify from the calling thread in step S112 of FIG. 9, and when notified from the calling thread in step S112, the process proceeds to step S314.
In step S314, the packet in the packet area is stored in the stack variable TMP. Here, since the MethodCall packet is stored in Step S312 when calling in Step S112 of FIG. 9, the MethodCall packet is stored in the stack variable TMP. Furthermore, null is assigned to the packet area of the record, and the process proceeds to step S315. In step S315, TMP is returned as a return value.
With this control, after the MethodCall packet received in step S112 is processed as the return value in step S108, the return value in step S112 is processed.

(4) Processing in Step S112 in FIG. 9 A case will be described in which, in step S112 in FIG. 9, the stub method execution unit 32 sets the GUI thread ID and the MethodCall packet as arguments and calls the exchangePacket method.
In step S302, since it is determined that the argument packet is not null, the process proceeds to step S304. In step S304, since INIT is TRUE by the calling operation in step S107, the process proceeds to step S306.

In step S306, it is determined that the argument is not an ActionReturn packet, and the process proceeds to step S308. In step S308, it is determined that the argument is not an ActionCall packet, and the process proceeds to step S312.
In step S312, the MethodCall packet is stored in the packet area of the record, and the process advances to step S313 after notifying the calling thread in step S108 of FIG. 9 that is waiting in step S313.
In step S313, the process waits for Notify from the calling thread in step S118 of FIG. 9 in step S312, and proceeds to step S314 when notified from the calling thread in step S118.
In step S314, the packet in the packet area is stored in the stack variable TMP. Here, since the MethodReturn packet is stored in step S312 when calling in step S118 of FIG. 9, the MethodReturn packet is stored in the stack variable TMP. Furthermore, null is assigned to the packet area of the record, and the process proceeds to step S315. In step S315, TMP is returned as a return value.
With this control, after the MethodReturn packet received in step S118 is processed as the return value in step S112, the return value in step S118 is processed.

(5) Processing in Step S118 in FIG. 9 A case will be described in which, in step S118 in FIG. 9, the GUI action execution unit 25 sets the GUI thread ID and MethodReturn packet as arguments and calls the exchangePacket method.
In step S302, since it is determined that the argument packet is not null, the process proceeds to step S304. In step S304, since INIT is TRUE by the calling operation in step S107, the process proceeds to step S306.

In step S306, it is determined that the argument is not an ActionReturn packet, and the process proceeds to step S308. In step S308, it is determined that the argument is not an ActionCall packet, and the process proceeds to step S312.
In step S312, the MethodReturn packet is stored in the packet area of the record, and the process advances to step S313 after notifying the calling thread in step S112 of FIG. 9 that is waiting in step S313.
In step S313, the process waits for Notify from the calling thread in step S122 of FIG. 9 in step S311, and when notified from the calling thread in step S122, the process proceeds to step S314.
In step S314, the packet in the packet area is stored in the stack variable TMP. Here, since the ActionReturn packet is stored in step S311 when calling in step S122 of FIG. 9, the ActionReturn packet is stored in the stack variable TMP. Furthermore, null is assigned to the packet area of the record, and the process proceeds to step S315. In step S315, TMP is returned as a return value.
With this control, after the ActionReturn packet received in step S122 is processed as the return value in step S118, the return value in step S122 is processed.

(6) Processing in Step S122 in FIG. 9 A case will be described where, in step S122 in FIG. 9, the action thread unit 31 sets an ActionReturn packet as an argument and calls the exchangePacket method.
In step S302, since it is determined that the argument packet is not null, the process proceeds to step S304. In step S304, since INIT is TRUE by the calling operation in step S107, the process proceeds to step S306.
In step S306, since the argument is an ActionReturn packet, the process proceeds to step S307. Here, ACTION_COUNT is decremented by 1 in step S307, ACTION_COUNT becomes “0”, and the process proceeds to step S309. In step S309, since ACTION_COUNT is “0”, the process proceeds to step S311.
In step S311, the ActionReturn packet is stored in the packet area of the record, and a Notify is made to the calling thread in step S118 of FIG. 9 that is waiting in step S313. Further, the record having the GUI thread ID as a key is deleted, and the process proceeds to step S315. In step S315, TMP is returned as a return value.
With this control, after the ActionReturn packet received in step S122 is processed as the return value in step S118, the return value in step S122 is processed.

(7) Processing in Step S207 in FIG. 10 This processing is the same as the processing in step S107 in FIG. 9 described above.

(8) Processing in Step S208 in FIG. 10 This is the same as the processing in step S108 in FIG. 9 described above.

(9) Processing in Step S212 of FIG. 10 A case will be described in which, in step S212 of FIG. 10, the stub method execution unit 32 sets the GUI thread ID and MethodCall packet packet as arguments and calls the exchangePacket method.
In step S302, since it is determined that the argument packet is not null, the process proceeds to step S304. In step S304, because INIT is TRUE by the calling operation in step S207, the process proceeds to step S306.

In step S306, it is determined that the argument is not an ActionReturn packet, and the process proceeds to step S308. In step S308, it is determined that the argument is not an ActionCall packet, and the process proceeds to step S312.
In step S312, the MethodCall packet is stored in the packet area of the record, and the process advances to step S313 after notifying the calling thread in step S208 of FIG. 10 that is waiting in step S313.
In step S313, the process waits for Notify from the calling thread in step S208 ′ of FIG. 10 in step S312, and proceeds to step S314 when notified from the calling thread in step S208 ′.
In step S314, the packet in the packet area is stored in the stack variable TMP. Here, since the ActionCall packet is stored in step S312 when the step S208 ′ of FIG. 10 is called, the ActionCall packet is stored in the stack variable TMP. Furthermore, null is assigned to the packet area of the record, and the process proceeds to step S315. In step S315, TMP is returned as a return value.
With this control, after the ActionCall packet received in step S208 ′ is processed as the return value in step S212, the return value in step S208 ′ is processed.

(10) Processing in Step S208 ′ in FIG. 10 A case will be described in which, in step S208 ′ in FIG. 10, the GUI action execution unit 25 ′ sets the GUI thread ID and the ActionCall packet as arguments and calls the exchangePacket method.
In step S302, since it is determined that the argument packet is not null, the process proceeds to step S304. In step S304, because INIT is TRUE by the calling operation in step S207, the process proceeds to step S306.
In step S306, it is determined that the argument is not an ActionReturn packet, and the process proceeds to step S308. In step S308, the argument is determined to be an ActionCall packet, and the process proceeds to step S310. In step S310, ACTION_COUNT is incremented by one, ACTION_COUNT becomes “2”, and the process proceeds to step S312. In step S312, the ActionCall packet is stored in the packet area of the record, and the process advances to step S313 after notifying the calling thread in step S212 of FIG. 10 that is waiting in step S313.
In step S313, the process waits for Notify from the calling thread in step S222 'of FIG. 10 in step S312, and when notified from the calling thread in step S222', the process proceeds to step S314.
In step S314, the packet in the packet area is stored in the stack variable TMP. Here, since the ActionReturn packet is stored in step S312 when step S222 ′ of FIG. 10 is called, the ActionReturn packet is stored in the stack variable TMP. Furthermore, null is assigned to the packet area of the record, and the process proceeds to step S315. In step S315, TMP is returned as a return value.
With this control, after the MethodCall packet received in step S222 ′ is processed as the return value in step S208 ′, the return value in step S222 ′ is processed.

(11) Processing in Step S222 ′ in FIG. 10 A case will be described in which, in Step S222 ′ in FIG.
In step S302, since it is determined that the argument packet is not null, the process proceeds to step S304. In step S304, because INIT is TRUE by the calling operation in step S207, the process proceeds to step S306.
In step S306, since the argument is an ActionReturn packet, the process proceeds to step S307. Here, ACTION_COUNT is decremented by 1 in step S307, ACTION_COUNT becomes “1”, and the process proceeds to step S312. In step S312, the ActionReturn packet is stored in the packet area of the record, and the process advances to step S313 after notifying the calling thread in step S208 ′ of FIG. 10 that is waiting in step S313.
In step S313, the process waits for Notify from the calling thread in step S218 of FIG. 10 in step S312, and proceeds to step S314 when notified from the calling thread in step S218.
In step S314, the packet in the packet area is stored in the stack variable TMP. Here, since the MethodReturn packet is stored in step S312 when calling in step S218 of FIG. 10, the MethodReturn packet is stored in the stack variable TMP. Furthermore, null is assigned to the packet area of the record, and the process proceeds to step S315. In step S315, TMP is returned as a return value.
With this control, after the MethodReturn packet received in step S218 is processed as the return value in step S222, the return value in step S218 is processed.

(12) Processing in Step S218 in FIG. 10 This processing is the same as the processing in step S118 in FIG. 9 described above.

  The information processing method according to the preferred embodiment of the present invention includes a request reply type communication from the GUI display module 10 to the business logic execution module 30 and a request reply from the business logic execution module 30 to the GUI execution module 20. Using the type of communication, a calculation result performed by the business logic execution module 30 can be reflected in the GUI application, triggered by an action event that has occurred on the GUI application.

  Thereby, even when the SSL client authentication is used to access the business logic execution module 30 from the information processing terminal 1 and the client certificate is installed in the GUI display module 10 of the information processing terminal 1, the GUI is installed. The execution module 10 can access the business logic execution module 30 by proxying the request by the request proxy unit 13.

  Thus, in the information processing method according to the preferred embodiment of the present invention, the GUI operation method and the business logic are executed in the information processing apparatus 2 only by displaying the GUI screen and receiving the input event in the information processing terminal 1. Therefore, it is possible to provide an information processing method that reduces the amount of development work on the information processing terminal 1 side and improves development efficiency.

(Modification)
As shown in FIG. 12, an information processing system 4a according to a modification of the best embodiment of the present invention includes an information processing terminal 1, a first information processing device 2a, and a second information processing device 2b. A GUI execution module 20 is mounted on the first information processing apparatus 2a. A business logic execution module 30 is mounted on the second information processing apparatus 2b.

  The information processing terminal 1, the first information processing device 2a, and the second information processing device 2b are connected via the first communication network 5a. The first communication network 5a is an external communication network such as the Internet, for example. The first information processing device 2a and the second information processing device 2b are connected via the second communication network 5b. The second communication network 5b is a communication network such as an in-house LAN.

  In the information processing system 4a according to the modified example of the best embodiment of the present invention, although overhead occurs in communication between the first information processing apparatus 2a and the second information processing apparatus 2b, The addition can be distributed by sharing the work between the first information processing apparatus 2a and the second information processing apparatus 2b.

(Other embodiments)
As described above, the best mode for carrying out the invention and the modifications thereof have been described. However, it should not be understood that the description and drawings constituting a part of this disclosure limit the present invention. From this disclosure, various alternative embodiments, examples, and operational techniques will be apparent to those skilled in the art.

  For example, the information processing terminal 1 and the information processing apparatus 2 described in the best embodiment of the present invention may be configured on one piece of hardware as shown in FIG. 3, or as shown in FIG. You may comprise on two hardware. Further, it may be configured on three or more hardware according to the function and the number of processes. Moreover, you may implement | achieve on the existing information processing system.

  It goes without saying that the present invention includes various embodiments not described herein. Therefore, the technical scope of the present invention is defined only by the invention specifying matters according to the scope of claims reasonable from the above description.

It is a figure explaining the outline | summary of the information processing system which concerns on the best embodiment of this invention. It is a figure explaining the process of the information processing method used for the information processing system which concerns on the best embodiment of this invention. It is a figure explaining the function structure of the information processing system which concerns on the best embodiment of this invention. It is a figure explaining the hardware constitutions of the information processing apparatus which concerns on the best embodiment of this invention. It is a figure explaining the object mounted in the information processing terminal which concerns on the best embodiment of this invention. It is a figure explaining the object mounted in the GUI execution module of the information processing apparatus which concerns on best embodiment of this invention. It is a class structure figure of the packet handled in the GUI execution module of the information processing apparatus which concerns on the best embodiment of this invention. It is a figure explaining the object mounted in the business logic execution module of the information processing apparatus which concerns on best embodiment of this invention. It is a sequence diagram which illustrates roughly the information processing method which concerns on the best embodiment of this invention. FIG. 6 is a sequence diagram schematically illustrating an information processing method according to the preferred embodiment of the present invention, and is a sequence diagram when an action event occurs from a method of a GUI object called from a business logic execution module. is there. It is a flowchart explaining the process of the start method of the communication object management part which concerns on the best embodiment of this invention. It is a figure explaining the function structure of the information processing system which concerns on the modification of the best embodiment of this invention. It is a figure explaining the outline | summary of the conventional information system.

Explanation of symbols

DESCRIPTION OF SYMBOLS 1 Information processing terminal 2, 2a, 2b Information processing apparatus 4, 4a Information processing system 5, 5a, 5b Communication network 10 GUI display module 11 Screen display part 12 Input part 13 Request proxy part 20 GUI execution module 21 GUI object part 22 GUI Method execution unit 23 GUI object management unit 24 Action event reception unit 25 GUI action execution unit 26 Communication object management unit 30 Business logic thread management unit 31 Action thread unit 32 Stub method execution unit 33 GUI stub management unit 34 Action management unit 35 Action execution Part 36 Business Logic Thread Management Department

Claims (5)

An information processing method used in an information processing system including an information processing device and an information processing terminal using information provided from the information processing device,
In the information processing terminal, a GUI screen is displayed on the information processing terminal in accordance with an instruction of the information processing device, and an input event is generated on the GUI screen;
In the information processing apparatus, when the occurrence of the input event is input, the input event is converted into a user action, and the user action is executed with a GUI object stub that is a stub of a GUI object corresponding to the input event. with threads is generated, a step of acquiring the GUI thread ID, the request agent unit of the information processing terminal, transmits the address and the GUI thread ID of the business logic execution unit for executing the business logic,
When the request proxy unit of the information processing terminal receives the address of the business logic execution unit and the GUI thread ID, it calls the business logic execution unit of the information processing device based on the received address and GUI thread ID. Performing the user action;
In the information processing apparatus, when the method of the GUI object is called in the execution of the user action, a new GUI screen is displayed on the information processing terminal based on the parameters related to the call, and the new GUI screen Generating a new input event,
In the information processing apparatus, when it is input that the new input event has occurred, the new input event is converted into return data, and the user action is executed in the thread based on the return data. And a step of outputting a result as a return value of the execution instruction of the user action. An information processing method used in an information processing system including an information processing device and an information processing terminal using information provided from the information processing device,
Storing a GUI object and a GUI object ID for identifying the GUI object in association with each other in the GUI object management unit of the GUI execution unit of the information processing apparatus;
In the action management unit of the business logic execution unit of the information processing device, storing a user action that occurs in the GUI object in association with an action ID that identifies the user action;
In the GUI stub management unit of the business logic execution unit of the information processing apparatus, storing the GUI object ID and a GUI object stub that is a stub of the GUI object associated with the GUI object ID in association with each other;
The GUI execution unit of the information processing apparatus displays a GUI screen on the information processing terminal based on the GUI object, and when an input event occurs on the GUI screen, the input event is transmitted to the information processing apparatus. Transmitting to the GUI execution unit;
When the GUI execution unit of the information processing apparatus receives the input event, it executes a GUI operation method based on the input event to generate a user action event, and acquires the action ID and GUI object related to the user action Steps,
In the GUI execution unit of the information processing device, generating a thread for executing the user action, initializing an action count variable, and acquiring a GUI thread ID;
In the GUI execution unit of the information processing device, transmitting the address of the business logic execution unit and the GUI thread ID to the request proxy unit of the information processing terminal;
In the request proxy unit of the information processing terminal, calling the business logic execution unit of the information processing device based on the address and the GUI thread ID;
In the GUI execution unit of the information processing apparatus, when the GUI thread ID, the action ID, and the GUI object are acquired, the GUI object ID is acquired from the GUI object management unit based on the GUI object, and Generating an action call packet including an action ID and the GUI object ID;
Transmitting in the GUI executing unit of the information processing apparatus, with increments the action count variable, the action call packet, the business logic execution unit of the information processing apparatus,
In the business logic execution unit of the information processing apparatus, when the action call packet is received, the action ID and GUI object ID are acquired from the action call packet, and the user action is acquired from the action management unit based on the action ID. And acquiring the GUI object stub from the GUI stub management unit based on the GUI object ID;
An information processing method comprising: executing the acquired user action on the acquired GUI object stub in the business logic execution unit of the information processing apparatus. In the business logic execution unit of the information processing apparatus, when a method of the GUI object stub is called from the user action with a predetermined parameter, a method call packet including the GUI object ID and the parameter is generated, Transmitting to the GUI execution unit;
In the GUI execution unit of the information processing apparatus, when the method call packet is received, the GUI object ID and the parameter are extracted from the method call packet, and the GUI object is extracted from the GUI object management unit based on the GUI object ID. A step to obtain,
In the GUI execution unit of the information processing apparatus, a new GUI screen is displayed on the information processing terminal based on the acquired GUI object and the parameter, and a new input event is generated on the new GUI screen Then, the new input event is transmitted to the GUI execution unit of the information processing apparatus, and converted into GUI object return data;
Generating a method return packet including the GUI object return data in the GUI execution unit of the information processing apparatus, and transmitting the method return packet to the business logic execution unit of the information processing apparatus;
In the business logic execution unit of the information processing apparatus, when the method return packet is received, the GUI object return data is acquired from the method return packet, and the GUI object return data is used as the return value of the method of the GUI object stub. The information processing method according to claim 2, further comprising the step of returning as: In the business logic execution unit of the information processing apparatus, when action return data is acquired as a return value of the method of the GUI object stub, an action return packet including the action return data is created, and the action return packet is used as the input event. Step to return as the return value of
The GUI execution unit of the information processing apparatus receives the action return packet, decrements the action count variable, and acquires the action return data from the action return packet when the action count variable becomes zero. The information processing method according to claim 3, further comprising: An information processing system comprising an information processing device and an information processing terminal using information provided from the information processing device,
The information processing terminal
In accordance with an instruction from the information processing device, a GUI screen is displayed on the display device of the information processing terminal, and an input event generated on the GUI screen by the input device of the information processing terminal is transmitted to the information processing device. ,
From the information processing apparatus, when receiving the address and GUI thread ID of the business logic execution unit for executing the business logic in the information processing apparatus, on the basis of the address and the GUI thread ID received, the information processing apparatus business logic Call the execution part,
The information processing apparatus includes:
A command to display the GUI screen is output to the information processing terminal, and when an input event occurs on the GUI screen, the input event is converted into a user action, and the business agent is sent to the request proxy unit of the information processing terminal. A GUI object stub that is a stub of a GUI object corresponding to the input event is transmitted in the business logic execution unit in response to a call from the request proxy unit of the information processing terminal by transmitting an address of the logic execution unit and a GUI thread ID Generating a thread for executing the user action, executing the user action in the thread,
When the method of the GUI object is called in the execution of the user action, a command to display a new GUI screen on the information processing terminal is output based on the parameters related to the call, and a new GUI screen is displayed. When a new input event occurs, the new input event is converted into return data, and a result of executing the user action in the thread based on the return data is output as a return value of the execution instruction of the user action. An information processing system characterized by this.

Images