This event causes the initiator of an I/O channel to shutdown the
channel. After terminating any outstanding actions, the initiator
must eventually send a
Closed event on the I/O channel.
Closed need not be generated as a direct response to
Close event. If the initiator is a server and the
network protocol supports this, the server may first send a close
message to the client and fire the
Closed event when the
confirmation is received from the client.
|Constructor and Description|
addCompletionEvent, associated, cancel, channels, channels, completionEvents, currentResults, defaultCriterion, forChannels, get, get, handled, handlingError, isCancelled, isDone, isEligibleFor, isStopped, processedBy, results, results, setAssociated, setChannels, setRequiresResult, setResult, stop, tieTo, toString
disableTracking, enqueued, firstResultAssigned, isTracked
clone, equals, finalize, getClass, hashCode, notify, notifyAll, wait, wait, wait