Content viewer latency
Reported by Ben Hood | June 9th, 2011 @ 06:35 AM
When you click through diff list, requests to retrieve the content for that entity are issued, but if the responses take a lot of time, this results in confusing slow updates to the content viewer panel. Short of caching these requests in the agent (see #259), we should probably:
-
Clear the content viewer or make the content visually opaque when a row is clicked. As well as this, a spinner should be displayed to indicate that a background task is being run.
-
If the user is clicking through the list faster than the remote call can be served, then the responses to any previous calls should be discarded so that they don't update the content viewer.
Comments and changes to this ticket
-
Ben Hood June 9th, 2011 @ 10:16 AM
- Tag set to “ui content-viewer”
-
Ben Hood June 9th, 2011 @ 10:17 AM
- Tag changed from “ui content-viewer” to “content-viewer, ui”
- Milestone cleared.
- Milestone order changed from “64” to “0”
-
Ben Hood July 1st, 2011 @ 11:55 PM
- Assigned user set to “Paul Jones”
- State changed from “new” to “resolved”
- Added a spinner;
- Added handling to abort a previous request;
-
-
Please Sign in or create a free account to add a new ticket.
With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.
Create new ticket
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile ยป
A Real Time Differencing Tool.
People watching this ticket
Ben Hood
Tags
Referenced by
-
259
Content request caching
See also #258 for a ticket relating to the client side
ha...