As a minimum, this object will contain a count of the total number of threads involved in the operation (via {@link #getThreadCount}) and the count of threads that have already finished (via {@link #getCompletedThreads}).
For operations involving data transfer, such as uploads or downloads, this object may also include a count of the total bytes being transferred (via {@link #getBytesTotal}) and a count of how many bytes have already been transferred (via {@link #getBytesTransferred}). The availability of this information is indicated by the result of {@link #isBytesTransferredInfoAvailable()}.
Further data tranfer information may be also available, such as the current transfer rate (via {@link #getBytesPerSecond()}) and an estimate of the time remaining until the transfer is completed (via {@link #getTimeRemaining()}). The availability of this information is indicated by the result of {@link #isTimeRemainingAvailable()}.
It is possible to cancel some operations. If an operation may be cancelled, this object will include a {@link CancelEventTrigger} (available from {@link #getCancelEventListener()}) which can be used to trigger a cancellation. Whether the operation can be cancelled is indicated by {@link #isCancelTaskSupported()}. @author James Murty
|
|
|
|
|
|