|
I like #2; give me an option to choose whether or not refresh the data.
Regards,
Barry Colson
--
Barry Colson | Sr. Programmer, Shared Services | Community Health Systems |4000 Meridian Blvd.
Franklin, TN 37067 | Tel: 615.628.6719 | Fax: 6153.465.36026 | barry_colson@xxxxxxx | http://www.chs.net
-----Original Message-----
From: WDSCI-L [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On Behalf Of Buck Calabro
Sent: Friday, December 19, 2014 8:28 AM
To: wdsci-l@xxxxxxxxxxxx
Subject: Re: [WDSCI-L] Outline is not using cached source?
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.
--
--buck
'I had nothing to offer anybody except my own confusion' - Jack Kerouac
--
This is the Rational Developer for IBM i / Websphere Development Studio Client for System i & iSeries (WDSCI-L) mailing list To post a message email: WDSCI-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives at http://archive.midrange.com/wdsci-l.
--------------------------------------------------------------------------
Disclaimer: This electronic message may contain information that is Proprietary, Confidential, or legally privileged or protected. It is intended only for the use of the individual(s) and entity named in the message. If you are not an intended recipient of this message, please notify the sender immediately and delete the material from your computer. Do not deliver, distribute or copy this message and do not disclose its contents or take any action in reliance on the information it contains.
--
This is the Rational Developer for IBM i / Websphere Development Studio Client for System i & iSeries (WDSCI-L) mailing list
To post a message email: WDSCI-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/wdsci-l.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
