[
https://issues.apache.org/jira/browse/TINKERPOP-2825?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stephen Mallette closed TINKERPOP-2825.
---------------------------------------
Resolution: Won't Do
Given the move to HTTP in 4.x I don't think we need to investigate this touchy
area of code without strong reason
> Examine delayed versus immediate reconnect for a Host
> -----------------------------------------------------
>
> Key: TINKERPOP-2825
> URL: https://issues.apache.org/jira/browse/TINKERPOP-2825
> Project: TinkerPop
> Issue Type: Improvement
> Components: driver
> Affects Versions: 3.5.4
> Reporter: Stephen Mallette
> Priority: Minor
>
> After TINKERPOP-2813 we have the original {{makeUnavailable()}} which offers
> an immediate {{Host}} uanvailability with delayed reconnect and
> {{tryReconnectingImmediately()}} which has an immediate reconnect and a
> delayed {{Host}} unavailability. Determine if the former is still required or
> if the latter is preferred for all cases. If nothing else, perhaps there is
> some refactoring there that might help remove some code,
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
