@ronaldjeremy Disconnecting the scope will still allow the controller to stay in memory and do whatever it needs to do, however, any changes to it’s scope won’t be reflected in the DOM while it’s disconnected. If the view’s controller shouldn’t be allowed to keep thinking in the background, then it shouldn’t be allowed to cache.
In you’re case I think you should be good, because those websocket messages would still be received by the controller and it would update its scope, but the updates wouldn’t be reflected in the DOM while it’s disconnected.
However, when you go back to the cached view then its scope would be reconnected, which it would then see that there are changes, and would then update the DOM with the new messages. Is this going to work in your scenario? Thanks.