Daniel Abramov

> Any workaround? Based on your comments, the only [temporary] dirty hack that comes to my mind is to wrap the `TcpStream` into another structure, implement `Drop` (or any other...

Yes, we still plan to work on it, but unfortunately we did not have time to work on it yet as it was lower in priorities than other things which...

Someone needs to update the #144 to the newest state (resolve the conflicts and fix some remarks in code), once it's done and clean, we could merge it. Unfortunately we...

The corresponding PR was closed as the author did not have to time to update it / address the remarks, so he decided to close the PR. The new PRs...

Current state: https://github.com/snapview/tungstenite-rs/issues/145#issuecomment-713581499

Just as a note: there was recently [a very similar discussion here](https://github.com/snapview/tungstenite-rs/issues/172#issuecomment-770500583).

Makes sense. Indeed, previously we "did not notice" this problem as first versions of `tungstenite-rs` did not allow to construct ping and pong messages directly.

I also proposed some idea in a comment to https://github.com/snapview/tungstenite-rs/pull/104, perhaps it would also be a solution.

@x1957 , awaiting a feedback from @agalakhov on https://github.com/snapview/tungstenite-rs/pull/104#pullrequestreview-345219851

There is #104 which is still open. Perhaps the best and simplest solution would be the one that has already been suggested by contributors in this issue, e.g. usage of...