Nathan
Even in the world of banking data can be stale (it takes time for the teller
to pick up your cheque, key it into a computer and then batch updates are
performed to update your account balance and down-date the payers account).
Same with online ordering, pick, despatch and invoicing processes (many of
which are run once a day in batch mode, and many on an AS/400).
Real time data, is there such a thing?
Maurice
-----Original Message-----
From: web400-bounces@xxxxxxxxxxxx [mailto:web400-bounces@xxxxxxxxxxxx] On
Behalf Of Nathan Andelin
Sent: 08 July 2008 22:17
To: Web Enabling the AS400 / iSeries
Subject: Re: [WEB400] Mapping SQL Result Sets to Browsers
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.
midrange.com
