Is there a way to get a websocket client with a bounded buffer?

[bowlofeggs]

Greetings!

I've noticed that the websocket client as created in the example repo seems to have a buffer somewhere inside it that is unbounded:

https://github.com/actix/examples/blob/c36d7371a96d2cfb8a7ff56d53ef3ba564140a29/websocket/src/client.rs#L23-L30

I've modified that program slightly so that it sends data rapidly to the server here:

bowlofeggs/examples@09bceb4

It also raises the timeout so that the server will give more time before hanging up the connection.

If you run the server and client (from my fork) and watch the client process's memory, you will see that it begins to use a lot of memory, and seemingly grows without bound.

I also observe that messages eventually stop getting to the server, though the memory continues to grow after this point.

Is there a way to get the client to be backed by a bounded buffer to control the memory usage?

[bowlofeggs]

I decided to file this as an issue: #1967