JobSyntax
Related Doc:
package dsl
Enqueues a job w/ the overriding details (instead of the ones from the submitting in scope)
Enqueues a job w/ the overriding details (instead of the ones from the submitting in scope)
the single result
'enqueue' is a convenience method which will then make a request against the matched worker and return that result.
'enqueue' is a convenience method which will then make a request against the matched worker and return that result.
Note: It is assumed that the 'enqueue' is used against a job w/ SubmissionDetails which specify only a single worker is chosen. If a mode is provided which returns multiple workers, then 'enqueueAll' is your darling.
the result type of the AsClient
the result from the single asClient worker
Similar to 'submit', but returns the responses from the worker.
Similar to 'submit', but returns the responses from the worker.
Submit the job, then on the (expected) redirect response, route the work to the given worker using the asClient
the response of the AsClient 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
eventually we'll get a collection of all the response futures (hence Future[List[Future]])
eventually we'll get a collection of all the response futures (hence Future[List[Future]])
an eventual collection of all the response futures
Syntax for submitting a job which will either return the first completed or
Exposes 'enqueue' and 'enqueueList' as a means to submit requests via an Exchange.
This is true for:
1) requests of type 'T' which have a Submitable type witness (the 'T' can produce a SubmitJob, which should be true for any T which can be converted to json)
2) there is a AsClient type witness for the request 'T', which just means something can take a request 'T' and produce a Future[Out] (for any type Out).