On 2016-10-20, <e...@zusammenkunft.net> wrote: > Even when a stream is not thread safe I try at least to make close() > safe/atomic as aborts and finalizers or shutdown hooks are natural > sources for concurrency – all using close().
true. > (However I guess it is less problematic for memory resources) In the case of SeekableInMemoryByteChannel close really only has effects on read/write operations, so it may not be that important in this case. Stefan --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org