Phoenix LiveView client state

Hello! I’m using server-side rendering virtual dom library similar to LiveView, called Replica. Library is very cool, but it miss one feature LiveView has. At the moment Replica can’t resume interactive state after client websocket disconnected. I’m curious how it’s usually is done in LiveView. In Replica, after client disconnected, corresponding server thread is terminated and state is collected by garbage collector. How you are dealing with it in LiveView? Not terminate immediately, or temporary store process data somewhere, and client can restore it using some sort of disposable credentials from his side? Thanks!