-
Notifications
You must be signed in to change notification settings - Fork 100
Open
Labels
1.0Pullrequests & issues related to the Typescript rewrite and 1.0 releasePullrequests & issues related to the Typescript rewrite and 1.0 release
Description
Expected Behavior
Remote peer is disconnected when calling this.socket.end()
in TcpDuplexConnection.close()
.
Actual Behavior
Some remote peers (clients) do not respect the end()
call and are able to still transmit data to the server, which results in NPEs and other undefined behavior.
This behavior was experienced from a .Net
TCP Client in Unity RSocket.
Steps to Reproduce
Not available.
Possible Solution
TcpDuplexConnection
may need to additionally, or in lieu of end()
, call destroy()
on this.socket
when close
is called.
Your Environment
- RSocket version(s) used: 1.0.0-alpha.1
- Other relevant libraries versions (eg.
netty
, ...): n/a - Platform (eg. JVM version (
javar -version
) or Node version (node --version
)): node: v16.13.1 - OS and version (eg
uname -a
): n/a
huahouye
Metadata
Metadata
Assignees
Labels
1.0Pullrequests & issues related to the Typescript rewrite and 1.0 releasePullrequests & issues related to the Typescript rewrite and 1.0 release