This repository has been archived by the owner on Aug 28, 2021. It is now read-only.
Unnecessary alert of closed SocketInputStream upon closing WebSocket. #6
Open
Description
Even when a WebSocket is gracefully closed, the given WebSocket's WebSocketListener still reports that...
Attempted to read from closed parent WebSocket SocketInputStream.
...even though the user 'knows' that/it just doesn't matter anymore.
For context, the console spits out these lines upon closing a WebSocket:
Received CLOSE frame, queuing closing of parent WebSocket...
Successfully closed the WebSocket.
Attempted to read from closed parent WebSocket SocketInputStream.
Fixing this could possibly be accomplished alongside issue #1, 'Improve the close-frame control flow'.