Mailing-List: contact user-help@curator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@curator.apache.org
From: Jordan Zimmerman <jordan@jordanzimmerman.com>
Content-Type: multipart/alternative;
 boundary="Apple-Mail=_D27B8581-293C-4709-85ED-ED53ED54A499"
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: DISCUSS: Remove Classic connection handling
Message-Id: <70DF7FF7-C510-432A-80CA-58EDC93B4A67@jordanzimmerman.com>
Date: Mon, 24 Jul 2017 00:01:29 -0500
To: dev@curator.apache.org,
 user@curator.apache.org
archived-at: Mon, 24 Jul 2017 05:01:44 -0000


--Apple-Mail=_D27B8581-293C-4709-85ED-ED53ED54A499
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Background: We are preparing to release what will be Apache Curator =
4.0.0. As usual, our tests are a bit flakey. Currently, the biggest =
culprit is "classic" connection handling. This is a special internal =
mode that most people probably don't even know about. It was added as a =
backward compatibility stop gap when the meaning of connection state =
LOST changed from Curator 2.x to Curator 3.x. With Curator 4.0, I'd like =
to completely remove "classic" connection handling unless there are =
objections. Here is the PR:

	https://github.com/apache/curator/pull/233 =
<https://github.com/apache/curator/pull/233>

Please comment on the PR if you have any issues with this. I'll leave =
this open for 48 hours - i.e. barring objections this will get merged =
Wednesday morning US time.

-Jordan=

--Apple-Mail=_D27B8581-293C-4709-85ED-ED53ED54A499
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dus-ascii"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" =
class=3D"">Background: We are preparing to release what will be Apache =
Curator 4.0.0. As usual, our tests are a bit flakey. Currently, the =
biggest culprit is "classic" connection handling. This is a special =
internal mode that most people probably don't even know about. It was =
added as a backward compatibility stop gap when the meaning of =
connection state LOST changed from Curator 2.x to Curator 3.x. With =
Curator 4.0, I'd like to completely remove "classic" connection handling =
unless there are objections. Here is the PR:<div class=3D""><br =
class=3D""></div><div class=3D""><span class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</span><a =
href=3D"https://github.com/apache/curator/pull/233" =
class=3D"">https://github.com/apache/curator/pull/233</a></div><div =
class=3D""><br class=3D""></div><div class=3D"">Please comment on the PR =
if you have any issues with this. I'll leave this open for 48 hours - =
i.e. barring objections this will get merged Wednesday morning US =
time.</div><div class=3D""><br class=3D""></div><div =
class=3D"">-Jordan</div></body></html>=

--Apple-Mail=_D27B8581-293C-4709-85ED-ED53ED54A499--