Definicja transactional buffer

Within the transactional context of the ESF, data should not be altered directly in the backend storage layer. To allow well-defined transaction handling, each modifying operation on ESF aspects is performed on a transactional buffer in the backend implementation of the <cool> service module. Each application provides buffered operation for each aspect. In some cases, where aspects have relations, a single buffer can buffer multiple aspects.

In the transactional buffer, it must be clear which modifying operation (such as insert, update, delete) was performed on which aspect row. Later on during the SAVE event, the application data is changed according to this buffer content, provided all checks during the BEFORE_SAVE event were successful. In addition to the transactional buffer, there needs to be another buffer to describe the locking status of the aspect rows that are used during the transactional context. For both the transactional buffer and the locking buffer, ESF convenience frameworks will allow the applications to create buffer instances for aspect and locking buffering in common, uncomplicated scenarios.