the subscription id of the remote runner
the remote runner which will match a worker based on the subscription
an uploader which can be used to upload data to the worker represented by the runner
the result of the execution
the rest client used to upload
the result of the execution
the remote runner which will match a worker based on the subscription
the subscription id of the remote runner
upload some data to a 'workspace' (e.g.
upload some data to a 'workspace' (e.g. consistent session/directory)
the workspace to which the data will be uploaded
the file name
the length of the source data to upload
the data source of the data to upload
the content type of the data
the timeout used to marshal the data into a request
a future of a success flag
Convenience method to upload a file
Convenience method to upload a file
the workspace (e.g. directory) where this should be uploaded
the data to upload
the timeout used to marshal the request
a future containing a success flag
an uploader which can be used to upload data to the worker represented by the runner
A data structure containing the result of an execution via the RemoteRunner.
The use-case driving this is to have a consistent, 'sticky-session' type workflow with a single worker which could still be either load-balanced via the exchange or targeted directly for subsequent requests.
The workflow used to produce a 'SelectionOutput' is this:
1) a job is submitted to the agora.api.exchange.Exchange 2) the job gets matched with some worker taking subscriptions. 3) we want to remember that worker, as well as proceed with executing the job from step 1
The SelectionOutput is the 'remembering' of that worker -- allowing us to submit using the same subscription (runner)
the subscription id of the remote runner
the remote runner which will match a worker based on the subscription
an uploader which can be used to upload data to the worker represented by the runner
the result of the execution