Implementing a web service application on a device with multiple threads

• US 7,680,877 B2
• Filed: 12/18/2006
• Issued: 03/16/2010
• Est. Priority Date: 12/18/2006
• Status: Active Grant

• Current Assignee: Ricoh Company Limited
• Original Assignee: Ricoh Company Limited
• Inventors: Tian, Lifen, Regnier, Alain, Wang, Yao-Tian
• Primary Examiner(s): Duong; Oanh
• Application Number:
  US11/641,510
• Publication Number:
  US 20080148258A1
• Time in Patent Office: 1,184 Days
• Field of Search: 709/202, 709/203, 709/217, 718/100
• US Class Current: 709/202
• CPC Class Codes: G06F 9/4843 by program, e.g. task dispatcher, supervisor, operating system
• CPC Class Codes: G06F 9/547 Remote procedure calls [RPC]; Web services
• CPC Class Codes: H04L 67/51 Discovery or management thereof, e.g. service location protocol [SLP] or web services

Abstract

Techniques are provided for efficiently processing SOAP requests at a Web service application (WSA) of a multi-functional device (MFP). In one technique, a WSA includes at least three threads. An external request processing thread processes SOAP requests from different client applications. A request processing thread processes a SOAP request according to the business logic of the WSA. A internal communications thread communicates with other components of the MFP that are distinct from the WSA. In another technique, a WSA processes different SOAP request differently, depending on the size of the SOAP and the resources required to process the SOAP request so that fast requests may be processed immediately while slow requests are pending. In another technique, a WS-Eventing specification is implemented within a WSA to simplify the event subscription and notification process.

Claims

1. A method for processing SOAP requests at a device, wherein the device comprises at least one service application that provides at least one service, the method comprising:

generating, at the service application;

an external request processing thread that receives the SOAP requests and dispatches the SOAP requests to at least one other thread;

fast and slow request processing threads that process SOAP requests according to business logic of the service application; and

an internal communications thread that communicates with a component of the device that is distinct from the service application;

waiting for and receiving, by the external request processing thread, a SOAP request of the SOAP requests, wherein the SOAP request is for the service and from a client application;

determining, by the external request processing thread, whether the SOAP request is of a first type or of a second type;

if the SOAP request is of the first type, then placing, by the external request processing thread, the SOAP request in a first queue for subsequent handling by a fast request processing thread that is dedicated to handling SOAP requests of the first type; and

if the SOAP request is of the second type, then placing, by the external request processing thread, the SOAP request in a second queue for subsequent handling by a slow request processing thread that is dedicated to handling SOAP requests of the second type;

processing, by the fast or slow request processing thread, the SOAP request; and

based on the SOAP request, sending, by the internal communications thread, a request to the component.

2. The method of claim 1, wherein the device includes a print process for processing print data and causing a printed version of an electronic document reflected in the print data to be generated.

3. The method of claim 1, wherein:

the device is a multi-functional peripheral (MFP) that comprises a plurality of service applications that includes the service application and that each provides at least one service;

a device facility manager (DFM) is associated with the MFP and handles device metadata requests from client applications that seeks services provided by the MFP; and

the DFM implements one or more Web Services protocols.

4. The method of claim 3, wherein the internal communications thread is dedicated to handling communication between the service application and the DFM.

5. The method of claim 1, wherein the internal communications thread is dedicated to handling communication between the service application and one or more platforms corresponding to the device.

6. The method of claim 1, further comprising the external request processing thread:

determining the type of the SOAP request; and

based on the type, dispatching the SOAP request to at least one of the fast or slow request processing threads or the internal communications thread.

7. The method of claim 1, further comprising the slow request processing thread:

waiting for requests to be dispatched to the slow request processing thread;

receiving the SOAP request;

determining the type of the SOAP request; and

based on processing the SOAP request, generating and sending a formatted response to the client application.

8. The method of claim 1, further comprising the internal communications thread:

waiting for requests to be dispatched to the internal communications thread;

receiving the SOAP request;

after sending the internal request to the component, receiving a response from the component; and

based on the response, sending a formatted response to the client application.

9. The method of claim 1, wherein the service application includes a master thread that generates and monitors the status of the external request processing thread, the fast and slow request processing threads, and the internal communications thread.

10. The method of claim 1, wherein the service application includes an event processing thread that:

registers events with an abstract layer of the service application;

waits for and receives indications of events from the abstract layer; and

composes and sends event notifications to an event sink.

11. A machine-readable storage medium for processing SOAP requests at a device, wherein the device comprises at least one service application that provides at least one service, the machine-readable storage medium carrying instructions which, when processed by one or more processors, causes:

generating, at the service application;

an external request processing thread that receives the SOAP requests and dispatches the SOAP requests to at least one other thread;

fast and slow request processing threads that process the SOAP requests according to business logic of the service application; and

an internal communications thread that communicates with a component of the device that is distinct from the service application;

waiting for and receiving, by the external request processing thread, a SOAP request of the SOAP requests, wherein the SOAP request is for the service and from a client application;

determining, by the external request processing thread, whether the SOAP request is of a first type or of a second type;

if the SOAP request is of the first type, then placing, by the external request processing thread, the SOAP request in a first queue for subsequent handling by a fast request processing thread that is dedicated to handling SOAP requests of the first type; and

if the SOAP request is of the second type, then placing, by the external request processing thread, the SOAP request in a second queue for subsequent handling by a slow request processing thread that is dedicated to handling SOAP requests of the second type;

processing, by the fast or slow request processing thread, the SOAP request; and

based on the SOAP request, sending, by the internal communications thread, a request to the component.

12. The machine-readable storage medium of claim 11, wherein the device includes a print process for processing print data and causing a printed version of an electronic document reflected in the print data to be generated.

13. The machine-readable storage medium of claim 11, wherein:

the device is a multi-functional peripheral (MFP) that comprises a plurality of service applications that includes the service application and that each provides at least one service;

a device facility manager (DFM) is associated with the MFP and handles device metadata requests from client applications that seeks services provided by the MFP; and

the DFM implements one or more Web Services protocols.

14. The machine-readable storage medium of claim 13, wherein the internal communications thread is dedicated to handling communication between the service application and the DFM.

15. The machine-readable storage medium of claim 11, wherein the internal communications thread is dedicated to handling communication between the service application and one or more platforms corresponding to the device.

16. The machine-readable storage medium of claim 11, wherein the instructions, when processed by the one or more processors, further cause:

determining, by the external request processing thread, the type of the SOAP request; and

based on the type, dispatching, by the external request processing thread, the SOAP request to at least one of the fast or slow request processing threads or the internal communications thread.

17. The machine-readable storage medium of claim 11, wherein the instructions, when processed by the one or more processors, further cause:

waiting, by the slow request processing thread, for SOAP requests to be dispatched to the slow request processing thread;

receiving, by the slow request processing thread, the SOAP request;

determining, by the slow request processing thread, the type of the SOAP request; and

based on processing the SOAP request, generating and sending, by the slow request processing thread, a formatted response to the client application.

18. The machine-readable storage medium of claim 11, wherein the instructions, when processed by the one or more processors, further cause:

waiting, by the internal communications thread, for SOAP requests to be dispatched to the internal communications thread;

receiving, by the internal communications thread, the SOAP request;

after sending the internal request to the component, receiving, by the internal communications thread, a response from the component; and

based on the response, sending, by the internal communications thread, a formatted response to the client application.

19. The machine-readable storage medium of claim 11, wherein the service application includes a master thread that generates and monitors the status of the external request processing thread, the fast and slow request processing threads, and the internal communications thread.

20. The machine-readable storage medium of claim 11, wherein the service application includes an event processing thread that:

registers events with an abstract layer of the service application;

waits for and receives indications of events from the abstract layer; and

composes and sends event notifications to an event sink.

21. A device for processing SOAP requests at the device, wherein the device comprises at least one service application that provides at least one service, the device being configured to:

generate, at the service application;

an external request processing thread that receives the SOAP requests and dispatches the SOAP requests to at least one other thread;

fast and slow request processing threads that process the SOAP requests according to business logic of the service application; and

an internal communications thread that communicates with a component of the device that is distinct from the service application;

cause the external request processing thread to wait for and receive a SOAP request of the SOAP requests, wherein the SOAP request is for the service and from a client application;

cause the external request processing thread to determine whether the SOAP request is of a first type or of a second type;

cause the external request processing thread to place the SOAP request in a first queue for subsequent handling by a fast request processing thread if the SOAP request is of the first type, wherein the fast request processing thread is dedicated to handling SOAP requests of the first type; and

cause the external request processing thread to place the SOAP request in a second queue for subsequent handling by a slow request processing thread if the SOAP request is of the second type, wherein the slow request processing thread is dedicated to handling SOAP requests of the second type;

cause the request processing thread to process the SOAP request; and

cause the internal communications thread, based on the SOAP request, to send a request to the component.

22. The device of claim 21, wherein the device includes a print process for processing print data and causing a printed version of an electronic document reflected in the print data to be generated.

23. The device of claim 21, wherein:

the device is a multi-functional peripheral (MFP) that comprises a plurality of service applications that includes the service application and that each provides at least one service;

a device facility manager (DFM) is associated with the MFP and handles device metadata requests from client applications that seeks services provided by the MFP; and

the DFM implements one or more Web Services protocols.

24. The device of claim 23, wherein the internal communications thread is dedicated to handling communication between the service application and the DFM.

25. The device of claim 21, wherein the internal communications thread is dedicated to handling communication between the service application and one or more platforms corresponding to the device.

26. The device of claim 21, being further configured to cause the external request processing thread to:

determine the type of the SOAP request; and

based on the type, dispatch the SOAP request to at least one of the fast or slow request processing thread or the internal communications thread.

27. The device of claim 21, being further configured to cause the slow request processing thread to:

wait for SOAP requests to be dispatched to the slow request processing thread;

receive the SOAP request;

determine the type of the SOAP request; and

based on processing the SOAP request, generate and send a formatted response to the client application.

28. The device of claim 21, being further configured to cause the internal communications thread to:

wait for SOAP requests to be dispatched to the internal communications thread;

receive the SOAP request;

after sending the internal request to the component, receive a response from the component; and

based on the response, send a formatted response to the client application.

29. The device of claim 21, wherein the service application includes a master thread that generates and monitors the status of the external request processing thread, the fast and slow request processing threads, and the internal communications thread.

30. The device of claim 21, wherein the service application includes an event processing thread that:

registers events with an abstract layer of the service application;

waits for and receives indications of events from the abstract layer; and

composes and sends event notifications to an event sink.