Implications of presenting large amounts of data to the user
Ideally, a transaction that updates files or databases should defer confirmation (to the user) until such updates are committed (by user syncpoint or end of task).
In cases where the application requires the reply to consist of a
large
amount of data that cannot all be viewed at one time (such as data
required
for browsing), several techniques are available, including:
- Terminal paging through BMS
- Using transient data queues