Total time
The total decompression time for the received data block will depend upon the data contained in the blocks. This can be estimated for the worst case condition where the most efficient type of run-length encoding has been conducted as previously explained. If double decompression buffers are employed, 40 segment cycle as listed in Table 6.1 will be required if each decompression buffer is 64 characters in size. By obtaining the time for the process cycle listed in Table 6.1 and multiplying by 40, the total decompression time can be estimated based upon the previous assumptions. If data is being received at 9600 bps, then 1200 cps (characters/s) are being received. At that data rate, ignoring control characters and retransmission time due to line errors, the received data-block buffer of 240 characters will be filled once every 0.2 (240/1200) s. This means that all of the previously discussed decompression processing as well as line handling and other communications functions must occur in that time or buffer queues must be employed to permit the processing of non-worst case conditions to be encountered which will then permit the processing to catch up with the data. By trade-offs of buffer size and timing and the employment of the double buffering, most compression routine, other than some of the Huffman and modified Huffman coding techniques, can be easily adapted to online processing.