madtheos
Hello Matt,
I worked on the Websocket implementation in REI3 so I think I can give a good answer. Because websocket is a persistent data-exchange connection between server & client, proxies can cause issues as they (often by default) disconnect clients after certain time limits.
But using Websocket as a prototocol does not necessitate by itself that the client needs to reload completely, when the connection breaks (as it does now). It was implemented like that, because our main focus is on onprem deployments and it was easier to reload the client after the connection was lost (which would almost never happen in local environments). When running REI3 publicly and with bad connections, this can become an issue - and because more organizations are using REI3 this way, we need to improve our code so that it can more gracefully handle these disconnects. Websocket connections will still die on disconnect and will require some time to re-establish themselves, but the client could handle this much better.
I do not have an ETA, when we will work on it - but it´s bugging me as well and I would love to be able to address it with our next feature release.