Results Queue Service
- HTTP Service
- Database Service
The Results Queue Service functions to allow other WATERS services to process results asynchronously. In a typical service request, the caller must wait for the service results to return before proceeding with further actions.
When processing large requests the time required for processing may cause server timeouts. The Results Queue Service is an alternative allowing callers to submit requests to a queue where processing is undertaken asynchronously. Results are then placed into the queue for pickup. Using an identification code, the user may query the Results Queue Service to either determine if processing is complete or fetch completed results.
The Results Queue Service has two modes, FETCH HTTP and GET STATUS which either attempt to return the queued service results or simply checks the status of processing service results.
|pQueueUniqueID||String||The service-defined identification number for a queued process. Obtained from a service call utilizing the optQueueResults parameter.|
|pQueueUserID||String||The alternative user-defined identification string assigned to a queued process. Obtained from a service call utilizing the optQueueID parameter.|
|pAction||String||Keyword of either FETCH HTTP or GET STATUS.|
Additional parameters specific to HTTP services are listed in the WATERS HTTP Services documentation.
Return Object The returned output from a FETCH HTTP action of the Results Queue Service is whatever the original service stored in the queue. When calling the service with the GET STATUS action, the return is an unformatted string text value of either Processing Complete Not Found Note that a value of "Not Found" may indicate that a given set of service results did process successfully but has since aged out of the cache and is no longer available.
Version: 2.0 - Released: January 4, 2010
- Initial Release of HTTP Services.