Details
-
Improvement
-
Status: Closed
-
Major
-
Resolution: Won't Do
-
3.2.2
-
None
-
None
Description
When the user submits a request with the "host" parameter it tells the driver to route the request to the value specified in that host. This feature is typically used internally by a remote traversal where the user wants to retrieve a side-effect (as the side-effect lives on the host the traversal was original executed on). Of course, if the host is unavailable for some reason when the user tries to retrieve their side-effect, the driver will result with an error.
Need to consider how to best handle this - perhaps the traversal could be re-submitted to a different host and iterated behind the scenes and thus allow the user to get their side-effect without knowing anything went bad?
See Client.chooseConnection() implementation for where this logic currently lives.