Web UI caching / update interval question
All,
I did a POC of RTC at work last week. One of the quirky things I noticed was that a work item updated in the Eclipse UI did not get reflected with its updated comments/changes in Firefox, even after multiple refreshes (using the refresh icon link, not F5).
- Has anyone seen this sort of behavior before?
- Is there a way to force the Web UI to look at the database for the latest version of a work item?
- Could the problem be at the Eclipse end, where changes are not immediately persisted to database in spite of a save?
- Could this be a problem with the caching implementation itself, wherein changes are kept in cache for an interval before being written in bulk to the database?
- How can this behavior be addressed so that changes are reflected globally so that anyone looking at a work item sees the change right away?
I appreciate your comments.
Thanks.
I did a POC of RTC at work last week. One of the quirky things I noticed was that a work item updated in the Eclipse UI did not get reflected with its updated comments/changes in Firefox, even after multiple refreshes (using the refresh icon link, not F5).
- Has anyone seen this sort of behavior before?
- Is there a way to force the Web UI to look at the database for the latest version of a work item?
- Could the problem be at the Eclipse end, where changes are not immediately persisted to database in spite of a save?
- Could this be a problem with the caching implementation itself, wherein changes are kept in cache for an interval before being written in bulk to the database?
- How can this behavior be addressed so that changes are reflected globally so that anyone looking at a work item sees the change right away?
I appreciate your comments.
Thanks.