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
With api calls where the response time is greater than the debounce time we can start a new call before the first has arrived, resulting in the old results arriving after the new ones. Old API calls to the same resource should be stopped when a new one is made. For instance, https://api.dataforsyningen.dk/gsearch_test/v1.0/adresse?q=frederik&limit=10 currently has a response time of ~7 seconds, but https://api.dataforsyningen.dk/gsearch_test/v1.0/adresse?q=frederik%207&limit=10 is only ~1 second.
The text was updated successfully, but these errors were encountered:
With api calls where the response time is greater than the debounce time we can start a new call before the first has arrived, resulting in the old results arriving after the new ones. Old API calls to the same resource should be stopped when a new one is made. For instance,
https://api.dataforsyningen.dk/gsearch_test/v1.0/adresse?q=frederik&limit=10
currently has a response time of ~7 seconds, buthttps://api.dataforsyningen.dk/gsearch_test/v1.0/adresse?q=frederik%207&limit=10
is only ~1 second.The text was updated successfully, but these errors were encountered: