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
Is your feature request related to a problem? Please describe.
Some requests to server resources are expected to take a long time (eg. requests for historical telemetry, large image downloads, etc) and need not block the UI. Other requests (such as requests for domain objects) should be relatively quick, and do block the UI. As such we should prioritize quick, UI blocking requests above slower non-blocking ones.
Describe the solution you'd like
Some browsers (eg. Chrome and Edge) support a priority option that allows code to provided hints about how to prioritize requests. We should use this to prioritize requests to Couch DB above requests to Yamcs by setting the priority to high. I will create a corresponding issue in the openmct-yamcs repo to set the priority to low.
I believe non-supporting browsers will just ignore the option (have tested with Firefox, and it did not throw an error) so no browser detection is necessary.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
Some requests to server resources are expected to take a long time (eg. requests for historical telemetry, large image downloads, etc) and need not block the UI. Other requests (such as requests for domain objects) should be relatively quick, and do block the UI. As such we should prioritize quick, UI blocking requests above slower non-blocking ones.
Describe the solution you'd like
Some browsers (eg. Chrome and Edge) support a
priority
option that allows code to provided hints about how to prioritize requests. We should use this to prioritize requests to Couch DB above requests to Yamcs by setting the priority tohigh
. I will create a corresponding issue in the openmct-yamcs repo to set the priority tolow
.I believe non-supporting browsers will just ignore the option (have tested with Firefox, and it did not throw an error) so no browser detection is necessary.
The text was updated successfully, but these errors were encountered: