|
I have to echo Simon's sentiment on refreshing the cache instead of tinkering the AG strategy. My reasoning runs along the lines that I create an AG to be as persistent as possible. I don't WANT to kill them and build them all day. I want that storage to last forever. If I find that I have some need to intervene and terminate an AG before the job, I re-think my design. I would write a new function that refreshes the cache rather than kill two activation groups. It may be the scalpel over the bulldozer, and a particular fetish of mine. It would be very interesting to hear some other experienced ILE developers' views on the idea that an AG should be as persistent as possible. --buck
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.