× 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.



Hi Reeve,

Actually the cache design is currently being redesigned and I will pass
along your comments to the appropriate developer.

I  would like to note that items that CODE caches are not just source
(verifiers can require very complex information relating to CCSIDs,
unicode, field lists and information and various other OS settings), and
that your proposal for "smart caching" may not work out to be quicker than
what is currently in place in these circumstances.  However, in the case
where actual members are being cached, the logic you present seems
reasonable.

Thanks,

Violaine Batthish
CODE Project Lead
batthish@ca.ibm.com          IBMCA(BATTHISH)

WDT/400 page:  http://www.ibm.com/software/ad/wdt400
WDT/400 Support : http://www.ibm.com/software/ad/wdt400/support




                    "Reeve Fritchman"
                    <reeve@ltl400.com>       To:     "CODE400-L@midrange. com" 
<CODE400-L@midrange.com>
                    Sent by:                 cc:
                    code400-l-admin@mi       Subject:     Program verify
                    drange.com


                    08/20/2001 04:35
                    PM
                    Please respond to
                    code400-l





This is a nice function the cache function is a little clumsy.  It might be
more useful with a few small modifications
"Refresh cache" should offer "yes", "no", and "smart".

"Yes" works the same as it appears to today: everything's reloaded.
"No" works the same as it appears to do today: nothing's reloaded.
"Smart" tells CODE/400 to compare the creation date of cached objects or
the
last-changed date of cached source with the creation date/last-changed date
of host object/source, if the host is available.  Only host objects newer
than the cached versions would be downloaded.

This functionality should shorten the refresh time substantially when only
one external object is changed (a prototype, for example).  Now the whole
shootin' match has to be reloaded; this is fine if you're around the corner
from your iBox and running 100 MB/sec networks.  Some of us work through
Internet connections, and any kind of Internet connection is slow when
you're downloading lots of little files.

Another possibility: how about defining an interface to the piece of
CODE/400 that reaches out and touches the iBox so we could build our own
refresh mechanisms?

Regards,
Reeve

_______________________________________________
This is the CODE/400 Discussion & Support (CODE400-L) mailing list
To post a message email: CODE400-L@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/cgi-bin/listinfo/code400-l
or email: CODE400-L-request@midrange.com






As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.