Stork may be nonresponsive when a large Kea configuration is fetched.
Stork has no limitation for the parallel refresh state requests. But popular web browsers can handle only 5 HTTP requests simultaneously.
If the fetching large Kea configuration is in progress and a user clicks the refresh buttons five times, the Stork UI will be non-usable. The user cannot go to any page that requires fetching some data (subnets, host reservations, dashboard) without refreshing a page.
I think that Stork should have only one active request for refresh state at the same time and present a loading spinner when refreshing is in progress.
