protected void payloadWritten(int payloadSize)
    {
        if (tc.isEntryEnabled())
            Tr.entry(tc, "payloadWritten", new Object[] { this, payloadSize });

        _unwrittenDataSize.addAndGet(-payloadSize);

        if (tc.isDebugEnabled())
            Tr.debug(tc, "unwrittenDataSize = " + _unwrittenDataSize.get() + " totalDataSize = " + _totalDataSize);
        if (tc.isEntryEnabled())
            Tr.exit(tc, "payloadWritten");
    }
protected void payloadWritten ( int payloadSize ) { if ( tc . isEntryEnabled ( ) ) Tr . entry ( tc , "payloadWritten" , new Object [ ] { this , payloadSize } ) ; _unwrittenDataSize . addAndGet ( - payloadSize ) ; if ( tc . isDebugEnabled ( ) ) Tr . debug ( tc , "unwrittenDataSize = " + _unwrittenDataSize . get ( ) + " totalDataSize = " + _totalDataSize ) ; if ( tc . isEntryEnabled ( ) ) Tr . exit ( tc , "payloadWritten" ) ; }
Informs the recovery log that previously unwritten data has been written to disk
by one of its recoverable units and no longer needs to be tracked in the unwritten
data field. The recovery log must use the supplied information to track the amount
of unwritten active data it holds.

This call is driven from the recoverable unit from which data has been written
and accounts for both the data and header fields necessary to write the data
completly.

Writing data in this manner will not change the total amount of active data contained
by the recovery log so only the unwritten data size will be effected.
The following example can be used to illustrate this. Consider that data items of sizes
D1, D2 and D3 have been added to an initially empty recovery log (see payloadAdded).
If H represents the size of all the header information that the underlying recoverable
units, sections and data items will need to form a persistent record of the data, then
the unwritten and total data size fields will be made up as follows:

unwritten total
D3 D3
D2 D2
D1 D1
H H

Suppose that the data item corrisponding to D2 has been written to disk. D2 + h2
(where h2 is any component of H that will no longer be required to form a
persistent record of the unwritten data) will be removed from the unwritten total so we
have:-

unwritten total
D3
D3 D2
D1 D1
H-h2 H

If the remaining data items are also written it should be clear that D3+h3 + D1+h1
bytes will also be removed from the unwritten total leaving it at zero. Also that
h1 + h2 + h3 = H.

@param payloadSize The number of bytes that no longer need to be written in order
to form a persistent record of the remaining unwritten data items
when a writeSections or forceSections operation is driven by the
client service.