the interface to an exchange so it can request more work or even cancel the subscription or return the job
the worker routes containing this handler
the details of the subscription
the http request context which contains the original HttpRequest, etc
the unmarshalled handler input
Replace the current handler logic with the new handler
Completing the request means sending a response back to the client and requesting another work item.
Completing the request means sending a response back to the client and requesting another work item.
The inner 'complete' thunk is lazy, so another work item will be requested even if the given lazily-evaluated return value throws an exception.
the lazy value to return, and upon the completion of which a new work item will be requested
this context (builder pattern)
completes this request, but doesn't request any more work from the exchange
completes this request, but doesn't request any more work from the exchange
the result
this work context
By calling 'completeWith', it assures that another work item will be requested when this future completes (whether successfully or not)
By calling 'completeWith', it assures that another work item will be requested when this future completes (whether successfully or not)
the response type
the response with which will be marshalled back to the client (and upon who's completion a new work item will be requested)
this context (builder pattern)
complete with the json value
complete with the json value
the value to complete
this context (builder pattern)
A convenience method to complete (return a result and request a new work item) with a byte source
the subscription details
the interface to an exchange so it can request more work or even cancel the subscription or return the job
a value 'A' for each multipart info/source pair to which this partial function applies
The match details associated with this request invocation.
The match details associated with this request invocation. As the endpoint is just a normal endpoint which could be invoked directly w/o having been redirected from an Exchange, it could be empty.
The MatchDetails are provided by values taken from the Http Headers.
the path specified for the handler
Replace the current subscription, effectively cancelling/creating a new subscription.
Replace the current subscription, effectively cancelling/creating a new subscription.
the new subscription
the updated work context w/ the new work subscription
The new subscription will be created, but no initial work items will be requested
the number of work items to request (typically 1, as we take one for each one we compute)
the Ack (if we indeed had a subscription key)
the unmarshalled handler input
the http request context which contains the original HttpRequest, etc
the worker routes containing this handler
the details of the subscription
Convenience function for 'replaceSubscription' which operates on the current subscription
Convenience function for 'replaceSubscription' which operates on the current subscription
the update subscription
the updated context with the new subscription
update the subscription which made this request using the given name/data value
update the subscription which made this request using the given name/data value
the subscription update
a future of the update
(Since version ) see corresponding Javadoc for more information.
Wraps the input to a computation, allowing the computation (mostly) to call 'request(n)' so it can request more work.
This class is analogous to a Subscription in Reactive Streams
the request type
the interface to an exchange so it can request more work or even cancel the subscription or return the job
the worker routes containing this handler
the details of the subscription
the http request context which contains the original HttpRequest, etc
the unmarshalled handler input