Blazor Server: Provide APIs/extensibility for circuit eviction
TheXenocide opened this issue · 3 comments
Is your feature request related to a problem? Please describe.
Idle users may be able to tie up significant system resources while not actually utilizing the application.
Describe the solution you'd like
Ideally we should be able to disconnect idle circuits, preferably with the opportunity to provide logic which can help identify/prioritize when and which connections can be safely but forcibly closed (e.g. identify if the user has a "dirty" entity and prevent eviction or perhaps only bother if resource utilization exceeds certain thresholds, etc.). It would also be nice to be empower client-side user experience indicators for activities related to this as well (e.g. modal warning which the user can cancel as well as css classes that could be used similar to components-reconnect-show, components-reconnect-failed, etc.)
We've moved this issue to the Backlog milestone. This means that it is not going to happen for the coming release. We will reassess the backlog following the current release and consider this item at that time. However, keep in mind that there are many other high priority features with which it will be competing for resources.
This is related to #30287
We've moved this issue to the Backlog milestone. This means that it is not going to be worked on for the coming release. We will reassess the backlog following the current release and consider this item at that time. To learn more about our issue management process and to have better expectation regarding different types of issues you can read our Triage Process.