Using these two values ties requests to a
particular query position within a panel, ensuring
that requests are canceled if:
- Duplicate requests with the same query are sent
- Requests from the same query position (but a
different query) are sent
The last point is important as it identifies
queries by a physical location in the dashboard
instead of with the query expression. If a
different query from the same position in a panel
is sent, the previous request should be canceled.
Using these two values ties requests to a
particular query position within a panel, ensuring
that requests are canceled if:
- Duplicate requests with the same query are sent
- Requests from the same query position (but a
different query) are sent
The last point is important as it identifies
queries by a physical location in the dashboard
instead of with the query expression. If a
different query from the same position in a panel
is sent, the previous request should be canceled.
Depending on context in the code, rename cacheKey
to exprID when it identifies a unique expression,
and rename cacheKey to requestID when it is
identifying a request.
Repeat requests, if they already exist in the
in-flight request map, will cause the previous
request to cancel.
The implementation of the unique key is the
responsibility of individual datasources.
stuart nelson