Message-ID: <gh-pgjdbc-pgjdbc-3506-c2633833098@github.com>
From: "vlsi (@vlsi)" <noreply+vlsi@github.com>
To: "pgjdbc/pgjdbc" <noreply+pgjdbc-pgjdbc@github.com>
Date: Tue, 04 Feb 2025 12:58:19 +0000
Subject: Re: [pgjdbc/pgjdbc] PR #3506: feat: Add access for global host status tracker
In-Reply-To: <gh-pgjdbc-pgjdbc-3506@github.com>
References: <gh-pgjdbc-pgjdbc-3506@github.com>
List-Id: <gh-pgjdbc-pgjdbc.github.com>
X-GitHub-Author-Login: vlsi
X-GitHub-Comment-Id: 2633833098
X-GitHub-Comment-Type: issue_comment
X-GitHub-Issue: 3506
X-GitHub-Repo: pgjdbc/pgjdbc
X-GitHub-Type: comment
X-GitHub-Url: https://github.com/pgjdbc/pgjdbc/pull/3506#issuecomment-2633833098
Content-Type: text/plain; charset=utf-8

>My solution only provides read access to the Map where the driver's view of hosts is stored. @vlsi, please explain how my solution affects pr https://github.com/pgjdbc/pgjdbc/pull/3409?

Your solution/suggestion is to make `GlobalHostStatusTracker` a part of the public API.
If we make load-balancing pluggable, it would be hard to retrofit `GlobalHostStatusTracker` for the cases when the status is stored in the plugin code. At the same time, the plugin might have its own vision on the topology, and so on.