commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Paul Burrowes (JIRA)" <>
Subject [jira] [Created] (COMPRESS-202) Document EOF behavior of TarArchiveInputStream
Date Thu, 27 Sep 2012 21:53:07 GMT
Paul Burrowes created COMPRESS-202:

             Summary: Document EOF behavior of TarArchiveInputStream
                 Key: COMPRESS-202
             Project: Commons Compress
          Issue Type: Wish
          Components: Documentation
            Reporter: Paul Burrowes
            Priority: Minor

When reading from a tar stream getNextEntry() returns null to signify EOF after reading the
first EOF record. This leaves the second EOF record in the stream unread potentially confusing
subsequent readers or blocking the writer trying to flush the stream in a piped configuration
e.g. network streaming.

The solution to this is to, if you care about subsequent data or true EOF, read from the underlying
InputStream until EOF or a protocol record marker.

It would be nice to have the documentation of TarArchiveInputStream mention that it does not
read the stream fully but stops at the first EOF record.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message