Hi,
Could we maybe cache the values in the SocketImpl/NIOSocketImpl
implementation?
IIRC we do something like that for SO_TIMEOUT already, since this
is handled at NIO level.
If we know the default value then setting one (when the other is
not set) could set it with the supplied value for the one, and
the default (or cached value) for the other?
Get would then return the cached value (or possibly default
value if not set?)
We could also potentially set some sensible defaults when creating
the socket.
Just some ideas..
best regards,
-- daniel
On 03/06/2023 08:19, Alan Bateman wrote:
On 02/06/2023 21:56, Terry Chow (Simba Technologies Inc) wrote:
Hi all,
I'm Terry and I'm from the mssql-jdbc driver team. I'd like to propose
some changes to JDK that would allow for keepalive extended socket
options support for Windows in order maintain feature parity within
the mssql-jdbc driver project. Currently, keepalive options are only
supported on Linux and Mac.
Just curious if your team has lobbied the Windows folks to provide the
equivalent of the TCP_KEEPIDLE and TCP_KEEPINTERVAL options so they
work like other platforms?
There is exploration in PR14232 on implementation these socket options
with SIO_KEEPALIVE_VALS but it will require disruptive changes in order
to make them to existing APIs.
-Alan
