You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 21, 2023. It is now read-only.
In the past, an event was triggered under the root scope to indicate whether or not the server data was ready for processing. This implementatoin was rather hackish in nature and was removed during UI restructuring as it was thought to be no longer needed (I thought wrong...)
A new implementation of the event should be considered to improve performance while returning the same functionality that was present in the old UI. Old listeners and triggers for the event may exist in some parts of the code and may be used if deemed compatible with whatever new implementation is used. If no performance issues or security concerns are present after further review of the prior mechanism, it may be re-used.
Most elements relying on this functionality are aesthetic or extra data (CPU usage meters, etc.). This receives a lower priority to core functionality yet should be fixed in the near future to prevent roadblocks and pointless race-time condition troubleshooting.
The text was updated successfully, but these errors were encountered:
In the past, an event was triggered under the root scope to indicate whether or not the server data was ready for processing. This implementatoin was rather hackish in nature and was removed during UI restructuring as it was thought to be no longer needed (I thought wrong...)
A new implementation of the event should be considered to improve performance while returning the same functionality that was present in the old UI. Old listeners and triggers for the event may exist in some parts of the code and may be used if deemed compatible with whatever new implementation is used. If no performance issues or security concerns are present after further review of the prior mechanism, it may be re-used.
Most elements relying on this functionality are aesthetic or extra data (CPU usage meters, etc.). This receives a lower priority to core functionality yet should be fixed in the near future to prevent roadblocks and pointless race-time condition troubleshooting.
The text was updated successfully, but these errors were encountered: