1 / 5

Compensation handling

Compensation handling. How to help application programmers to write fault tolerant systems using exception handling, abort and compensation?. Abort - transactional objects (transparent during runtime, transparent for development)

trula
Download Presentation

Compensation handling

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Compensation handling How to help application programmers to write fault tolerant systems using exception handling, abort and compensation?

  2. Abort - transactional objects (transparent during runtime, transparent for development) Compensate - compensatable objects/operations (transparent during runtime, not transparent for development) Exception handling - program/application recovery, general technique, part of system development (not transparent during runtime, not transparent for development)

  3. Too many. Error recovery is too complex. And error prone. The mess needs cleaning up. A, C, EH: - Different levels? - Different faults? - Different aims? - Different cost?

  4. How do they work together? In which order? What is the minimal (or reasonable) set of recovery means? Not everything can be or needs to be aborted or compensated for. We do not live in such a world. (Is compensation enough?) You can do without C but you cannot do without EH. Choice of the right mixture of abort, compensation and EH is application specific.

  5. Programmers need to know when a transaction was aborted - we clearly need an abort exception here: methods return an exception if they cannot return results - actions return an exception if they have been aborted (with or without compensation). System structuring out of actions is a good idea. In the world of EH they are called nested exception handling contexts.

More Related