You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Note that the server-side ws-send! succeeds despite occurring immediately after a use of ws-close!. This seems unhelpful.
The text was updated successfully, but these errors were encountered:
lexi-lambda
changed the title
ws-close! fails to close ports if the client has closed the connectionws-send! silently fails if the connection is closed
Oct 9, 2024
Actually looking at the source: this seems to be intended behavior. rfc6455-send! checks if the connection is closed, and if it is, it does nothing and returns. I find this quite unintuitive: I would expect an exception to be raised, as when writing to a closed output port. At the very least, it would be nice to document the behavior.
The following program runs without errors:
Note that the server-side
ws-send!
succeeds despite occurring immediately after a use ofws-close!
. This seems unhelpful.The text was updated successfully, but these errors were encountered: