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.)
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.)