Richard Hodges

That would be "terminal" cancellation. "total" means that the cancellation happened without causing observable side effects. I believe we can do this in the websocket stream because we buffer internally....

The default cancellation mode requested is "all" which implies "total | partial | terminal", so the implementation is free to implement the one it is best able to do and...

> What good is canceling if the behavior is unpredictable, i.e. sometimes it works and sometimes it doesn't? This is inescapable in an asynchronous system. I have the feeling that...

I didn’t mean to imply that cancellation can be arbitrarily downgraded. The caller is free to request “any kind of cancellation” of course. This is the default. But the user...

For the timebeing, you can call `shutdown()` or `close()` on the underlying socket. This will cause the async_read to complete with an error. Another way to stop in a more...

It's not quite that simple. During an async_read operation, quite a few underlying async sub-operations can happen, including reading and writing of control frames and continuation of write and close...

>> It is possible to implement terminal cancellation without a huge amount of difficulty, but this gives you nothing more than you already have by closing the underlying socket, since...

There is a fix for this issue in the pipeline.

Thanks for the query. Are you able to provide more information on what you are trying to do? Are you saying that you want to write a websocket proxy?

OK, this looks reasonably straightforward.