-
Notifications
You must be signed in to change notification settings - Fork 57
Unix sockets for JVM #539
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Unix sockets for JVM #539
Conversation
public IPAddress? LocalAddress { get; private set; } | ||
public int? LocalPort { get; private set; } | ||
public string? LocalPath { get; private set; } | ||
public abstract EndPoint EndPointImpl { get; } |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
(Minor) Is there a reason to not call this EndPoint
, without Impl
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I try to avoid naming variables/properties the same as types to reduce confusion. Though, I do not like the Impl
, so we can rename them.
Return old frameworks. Marked everything related to `UnixDomainSocketEndPoint` with `#if NET8_0_OR_GREATER` pragma.
Otherwise, it was possible that we acknowledge receival of a huge data chunk via PkgInputStream, but prematurely stop processing of this chunk in readMsg, because the socket was disconnected in-flight.
…ort both TCP and Unix socket addresses
…traction and update related logic
…e `SocketWire` implementations accordingly
e724525
to
e29a625
Compare
No description provided.