RoutingClient
Related Docs:
object RoutingClient
| package exchange
Similar to 'submit', but returns the result from the worker.
Similar to 'submit', but returns the result from the worker.
This assumes the job submitted to the exchange can be sent verbatim to the worker.
The workflow is:
1) submit to exchange, awaiting a match 2) on (redirect) response (when a worker is eventually assigned), submit the work to the matched worked 3) return the response from the worker ... which could be *anything*
the job submission
the worker response
Submit the job, then on the (expected) redirect response, route the work to the given worker using the 'sendToWorker'
Submit the job, then on the (expected) redirect response, route the work to the given worker using the 'sendToWorker'
the job to submit
the function used to send work to the worker (which may or may not have been the same request)
both the original work submission response and the response from the worker
Convenience method for enqueueing the request, awaiting for a single worker and then returning the unmarshalled response
Convenience method for enqueueing the request, awaiting for a single worker and then returning the unmarshalled response
the response type
the job to submit
the single unmarshalled response
Encapsulate the exchange client workflow of: 1) submit a request to the exchange 2) have a response telling it where it should go 3) submitting a request to that redirected location 4) returning 'CompletedWork', which contains the worker(s) and their responses