Fwd: Thread interruption while reading from a ZipFS entry will close the entire FS

[Bruno Ploumhans]

> I don't think that would make sense. The reason the thread has been interrupted is because something wants to cancel what it are doing as quickly as possible. It's important that operations on network channels that block indefinitely are interruptible.

Would the same hold say for a file that is accessed via the network?
Maybe in those cases the file access is actually a network operation
in disguise.

> The discussion is focused on FileChannel as it is somewhat questionable whether it should have been an InterruptibleChannel in the first place.

It sounds questionable, yes. Is this something that can be changed now?

Bruno