XHRs still active when the page context is exited are terminated with status code 0. These events are presently reported to application code as errors and may cause unsightly error messages.
Repeated calls to get() on the same object (but with force_refresh=true or different view/filter paramerers) will cancel previous GET requests if they are unfinished and send errors with dojoType==='cancel' to the application code. These events should be consistently processed within the library itself; note however that it is not clear whether promises from the prior GETs should be resolved and how, as it is not guaranteed that promise from the old GET has the same callbacks associated with it as the new one.
XHRs still active when the page context is exited are terminated with status code 0. These events are presently reported to application code as errors and may cause unsightly error messages.
Repeated calls to get() on the same object (but with force_refresh=true or different view/filter paramerers) will cancel previous GET requests if they are unfinished and send errors with dojoType==='cancel' to the application code. These events should be consistently processed within the library itself; note however that it is not clear whether promises from the prior GETs should be resolved and how, as it is not guaranteed that promise from the old GET has the same callbacks associated with it as the new one.