You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@curator.apache.org by "Jordan Zimmerman (JIRA)" <ji...@apache.org> on 2017/07/26 13:56:02 UTC

[jira] [Resolved] (CURATOR-427) Remove ClassicConnectionHandling

     [ https://issues.apache.org/jira/browse/CURATOR-427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jordan Zimmerman resolved CURATOR-427.
--------------------------------------
    Resolution: Fixed

> Remove ClassicConnectionHandling
> --------------------------------
>
>                 Key: CURATOR-427
>                 URL: https://issues.apache.org/jira/browse/CURATOR-427
>             Project: Apache Curator
>          Issue Type: Improvement
>          Components: Client, Framework
>    Affects Versions: 3.3.0
>            Reporter: Jordan Zimmerman
>            Assignee: Jordan Zimmerman
>             Fix For: 4.0.0
>
>
> ClassicConnectionHandlingPolicy was a stop-gap from Curator 2.x to Curator 3.x. Now that we're at 4.0 there's no reason to maintain it. It necessitates running the tests twice and is a headache to stay compatible. StandardConnectionHandlingPolicy is what users expect anyway.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)