Abstract:
An approach is provided for managing the processing of print data at a printing device based upon available consumable resources. A printing device includes a print process configured to determine consumable resources that are currently available at the printing device. The print process is further configured to determine which print data is to be processed based upon the consumable resources currently available at the printing device and the consumable resources required to completely process each of the print data. Print data that can be completely processed using the currently available consumable resources are selected for processing. The print process may also be configured to cause a notification to be provided to a client device to indicate the consumable resources currently available at a printing device and/or that insufficient consumable resources were available to process particular print data and to recommend other consumable resources to process the particular print data.
Abstract:
Approaches for the optimized printing of electronic documents are provided. The approaches are applicable to a wide variety of contexts and implementations and include generating an estimated processing time for an electronic document and reporting the estimated processing time back to a client device. Generating an estimated time to process includes processing at least a portion of the print data. Further, the approaches include re-ordering a processing queue based on the estimated processing time for the electronic document, and additionally based on an in-queue time for each print data in the processing queue. Further, any user-designated priority may be factored into the re-ordering of print data in the processing queue, or in the alternative, bypass the optimization process entirely. These approaches may be implemented on a printing device, a print server, a client device or any other device capable of utilizing these approaches.
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.
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.
Abstract:
A device management system is provided for processing client requests. When a client request is received, the device management system selects a particular network device from a plurality of available network devices to process the request. The selection is based upon user preference data and network device attribute data. The user preference data indicates one or more attributes that a user associated with the client request would like a network device that processes the request to have. The user preference data may also indicate a relative priority of desired network device attributes. The network device attribute data indicates one or more attributes of the plurality of available network devices. Examples of the attributes indicated by the user preference data and device attributes include performance attributes, such as resolution, speed and finishing options, as well as other device attributes, such as location.
Abstract:
Systems and methods are disclosed for enabling legacy devices to consistently and reliably operate within a distributed scan environment using proxy scan services. A proxy scan service is communicatively coupled between a scan management service and a scanner. Information transmitted between the scan management service and the scanner is intercepted at the proxy scan service, where the scan management service recognizes a first format message for the information and the scanner recognizes a second format message for the information. The information is converted at the proxy scan service between the first format message and the second format message. The transmission between the scan management service and the scanner is completed using the converted information.
Abstract:
Systems and methods are disclosed for scanning devices to exchange scan messages with external devices, where the scan messages comprise WS-Scan protocol message and DSM protocol messages. A determination is made if a scan message comprises a WS-Scan protocol message or a DSM protocol message. A response is made to the WS-Scan protocol message if the scan message is a WS-Scan protocol message. Further, a response is made to the DSM protocol message if the scan message is a DSM protocol message. A user interface of the scanning device hides the distinctions between WS-Scan and DSM to permit a user to seamlessly select scanning to either or both WS-Scan and DSM destinations.
Abstract:
Systems and methods are disclosed for scanning devices to exchange scan messages with external devices, where the scan messages comprise WS-Scan protocol message and DSM protocol messages. A determination is made if a scan message comprises a WS-Scan protocol message or a DSM protocol message. A response is made to the WS-Scan protocol message if the scan message is a WS-Scan protocol message. Further, a response is made to the DSM protocol message if the scan message is a DSM protocol message. A user interface of the scanning device hides the distinctions between WS-Scan and DSM to permit a user to seamlessly select scanning to either or both WS-Scan and DSM destinations.
Abstract:
Systems and methods are disclosed for enabling legacy devices to consistently and reliably operate within a distributed scan environment using proxy scan services. A proxy scan service is communicatively coupled between a scan management service and a scanner. Information transmitted between the scan management service and the scanner is intercepted at the proxy scan service, where the scan management service recognizes a first format message for the information and the scanner recognizes a second format message for the information. The information is converted at the proxy scan service between the first format message and the second format message. The transmission between the scan management service and the scanner is completed using the converted information.
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.