×
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.
Walden H. Leverich wrote:
You can cache object references to increase performance,
but then you have a question of currency, the cached version
may not be the database version, and this is something one
has to account for in the design.
Both the wording and the concept expressed there caught my attention.
The wording could imply that object references could go stale, and need
to be reinstantiated. Is that the case? Or that attributes could go
stale and need to be refreshed from the database?
The concept get's really interesting in high-volume,
transaction-oriented environments. Again my background in banking comes
to mind. The database is being updated every minute of the day from
Internet, ATM, Over The Counter, ACH, Credit Card and Debit Card
Merchants, Payroll Deposits, Check Clearing, Interbank Transfers, ...
the list could go on.
You almost never like to let the data on the screen go stale.
Nathan.
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
