Setting aside the fact that WebSockets are a well-defined mechanism for maintaining a persistent long-running connection to a web server…
This is how .NET Blazor works (for one of its modes), where all rendering and processing is done server-side, and the client just has a small JS/WASM bundle that posts updates to the DOM, and sends DOM events to the server. And it’s ASS.
Setting aside the fact that WebSockets are a well-defined mechanism for maintaining a persistent long-running connection to a web server…
This is how .NET Blazor works (for one of its modes), where all rendering and processing is done server-side, and the client just has a small JS/WASM bundle that posts updates to the DOM, and sends DOM events to the server. And it’s ASS.