KITLGO: a generic logging service

A generic logging service should center to the variable and even antagonistic needs of clients, without imposing unnecessary overhead on clients that do not use all of its functions. A solution to this problem, called K_I^TL_G^O, is described in detail. It solves the problem by separating logging characteristics into five mechanisms: buffering policy, distribution of records, replication of records, sharing of logs, and management of physical media. Each characteristic is embodied in a class. For each class, multiple policy implementations can be provided. Instances of these classes are stackable in any appropriate number or order. A client customizes his log to a particular set of failure assumptions by selecting adequate classes, instantiating them, and connecting the instances together