Message-ID: <gh-pgjdbc-pgjdbc-2923-c1613391690@github.com>
From: "vlsi (@vlsi)" <noreply+vlsi@github.com>
To: "pgjdbc/pgjdbc" <noreply+pgjdbc-pgjdbc@github.com>
Date: Thu, 29 Jun 2023 15:26:19 +0000
Subject: Re: [pgjdbc/pgjdbc] PR #2923: un-deprecate SSL_FACTORY_ARG
In-Reply-To: <gh-pgjdbc-pgjdbc-2923@github.com>
References: <gh-pgjdbc-pgjdbc-2923@github.com>
List-Id: <gh-pgjdbc-pgjdbc.github.com>
X-GitHub-Author-Login: vlsi
X-GitHub-Comment-Id: 1613391690
X-GitHub-Comment-Type: issue_comment
X-GitHub-Issue: 2923
X-GitHub-Repo: pgjdbc/pgjdbc
X-GitHub-Type: comment
X-GitHub-Url: https://github.com/pgjdbc/pgjdbc/pull/2923#issuecomment-1613391690
Content-Type: text/plain; charset=utf-8

>So the proposal is to leave the deprecation as it is and add a Properties based constructor?

That is my intention. I would like people to refrain from accidentally using sslsocketfactoryarg even though we will have to support it for the indefinite future.