Replies: 2 comments 1 reply
-
|
Supplementary reason: There are many Plugins that are stateful, and startup is time-consuming, and frequent restarts lead to poor experience |
Beta Was this translation helpful? Give feedback.
-
|
The backend always treats a reconnecting client (one that was temporarily disconnected) in the same way as a new client. Since Theia starts a new plugin host for each new client, it will also start a new plugin host for reconnecting clients. I don't think there's currently a way around that without some refactoring of the networking code. You can create a feature-request for that, contributions are always welcome :) |
Beta Was this translation helpful? Give feedback.
-
My idea is to generate a session id for each browser tab to indicate identity, so that it can distinguish between reconnection and new opening (refresh is considered a new opening). After the disconnection, a dialog is used to prevent user operations, and the network request during the disconnection process is recorded through the queue, and then replayed after recovery. The default longest recovery time is 15s. |
Beta Was this translation helpful? Give feedback.
-
Why does Plugin need to restart after the network is disconnected? It may just be a short-term network failure. If there is a way to prevent user operations after a short network disconnection, is it possible to reconnect without restarting the plugin process?
Beta Was this translation helpful? Give feedback.
All reactions