summaryrefslogtreecommitdiffstats
path: root/libart/src
diff options
context:
space:
mode:
authorNeil Fuller <nfuller@google.com>2014-04-11 17:16:30 +0100
committerNeil Fuller <nfuller@google.com>2014-04-22 14:34:41 +0100
commitf0d40d662d9dfdb04215c718961765837d2cf00c (patch)
tree60550f24d5ec0eeb8bbdad8d17e08c4bb3798d4a /libart/src
parent5d5c657b0101123d8c4de4a316f50a2a76c41a46 (diff)
downloadlibcore-f0d40d662d9dfdb04215c718961765837d2cf00c.zip
libcore-f0d40d662d9dfdb04215c718961765837d2cf00c.tar.gz
libcore-f0d40d662d9dfdb04215c718961765837d2cf00c.tar.bz2
libcore changes to support asynchronous close interruption
Previously AsynchronousSocketCloseMonitor was used to handle socket interruption on close. To support the same for FileChannel it has been renamed to AsynchronousCloseMonitor. The Java class was already called this. FileInputStream, FileOutputStream, RandomAccessFile will now throw IOException if a connection is closed by another thread during read. Thread.interrupt() continues to have no effect on streams. FileChannel will now throw AsynchronousCloseException during reads and writes if the file is closed, per the documentation. FileChannel will now throw ClosedByInterruptException during reads and writes if the thread reading/writing is interrupted. Note: FileChannel.lock() will probably still not not throw AsynchronousCloseException, though it probably should. This change also has impact on external/conscrypt and frameworks/base. Change-Id: I37de3e7d1a005a73821221e6156d10b95c595d7a Bug: 13927110
Diffstat (limited to 'libart/src')
0 files changed, 0 insertions, 0 deletions