On Mon, 2013-02-04 at 00:46 -0500, Nathan Scott wrote:
> ...
> > - consider defaulting to PCP_SECURE_SOCKETS=1
>
> The semantics of that env var are that if a secure connection cannot
> be established, the connection fails. That seemed like the right way
> to approach it (people who might want to be using this would want to
> be sure it doesn't silently fallback to not-secure, in order to not
> regress existing installations on upgrade).
>
> Given that, and the requirements for backwards compatibility when we're
> operating in environments with down-rev remote hosts, I'm not sure we
> can switch this mode to default ... thoughts? Perhaps down the track,
> when we are confident the vast majority of installations have these
> capabilities (and we have gained more production-system-type confidence
> in the new code!).
I agree with Nathan ... the obligation to NOT break production
environments with mixed PCP versions installed across servers and
clients is of paramount importance.
This is even more so when we're talking about new features that are not
battle scarred across the production landscape.
|