×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
On 12/18/2014 5:57 PM, Edmund Reinhardt wrote:
For those who care, reply and tell me if you think the outline view should
use cached (potentially) stale data on the initial load and only get from
the host if the cache doesn't have it, or the refresh button is pressed.
Email and say "CHANGE"
CHANGE.
I deeply understand the trade-off being made here and don't find it
'wrong' to hit the host for the most accurate information. I would,
however, use the cache whenever possible: that's the point of having a
cache.
If it were my code, I'd ponder a couple of choices:
1) On initial load, refresh the cache with all the files being referred
to for the outline. Pro: Cache gets refreshed; a second load will be
much faster. Con: It takes time to refresh the cache.
2) Use the (possibly stale) cache but put up a message that the cache
was not checked for staleness and that F5 might be advisable. Pro: Fast
load. Con: Possibly incorrect outline. Pro: User can choose how to proceed.
3) Create a preference for the Outline View that clearly indicates how
to drive this behaviour. Pro: Let the user decide. Con: Another
preference to code and understand. Also, a preference is global;
sometimes I just don't care about the outline view and I'm OK with the
fact that it's stale.
Again, I don't find the current behaviour 'wrong' - it's a trade-off and
those decision points invariably disappoint someone.
midrange.com
