I don't think the memory waste is the problem in this case, a websocket is a long lived connection. If you mix it with regular requests and don't think about th

I don't think the memory waste is the problem in this case, a websocket is a long lived connection. If you mix it with regular requests and don't think about the concurrency consequences you'll be able to serve 1 request and then allow for 1 websocket connection and your done. All other connections will be pending until the websocket is closed.