Re: [compress] Need API Feedback/Advice for ZipArchiveOutputStream ans ZIP64

2011-08-09 Thread Stefan Bodewig
On 2011-08-09, Phil Steitz wrote: > On 8/8/11 11:29 PM, Stefan Bodewig wrote: >> On 2011-08-08, Phil Steitz wrote: >>> As a test of whether or not it will work, I would recommend writing >>> the javadoc and test cases first (which of course we all do any way ;) >> Javadocs are there now with svn

Re: [compress] Need API Feedback/Advice for ZipArchiveOutputStream ans ZIP64

2011-08-09 Thread Phil Steitz
On 8/8/11 11:29 PM, Stefan Bodewig wrote: > On 2011-08-08, Phil Steitz wrote: > >> As a test of whether or not it will work, I would recommend writing >> the javadoc and test cases first (which of course we all do any way ;) > Javadocs are there now with svn rev 1155223, in particular >

Re: [compress] Need API Feedback/Advice for ZipArchiveOutputStream ans ZIP64

2011-08-08 Thread Stefan Bodewig
On 2011-08-08, Phil Steitz wrote: > As a test of whether or not it will work, I would recommend writing > the javadoc and test cases first (which of course we all do any way ;) Javadocs are there now with svn rev 1155223, in particular

Re: [compress] Need API Feedback/Advice for ZipArchiveOutputStream ans ZIP64

2011-08-08 Thread Stefan Bodewig
On 2011-08-08, Phil Steitz wrote: > On 8/6/11 9:30 PM, Stefan Bodewig wrote: >> On 2011-08-06, Phil Steitz wrote: >>> On 8/5/11 9:40 PM, Stefan Bodewig wrote: InfoZIP's ZIP has decided to make it an option for the whole archive (the command line doesn't offer much flexibility here) and

Re: [compress] Need API Feedback/Advice for ZipArchiveOutputStream ans ZIP64

2011-08-07 Thread Phil Steitz
On 8/6/11 9:30 PM, Stefan Bodewig wrote: > On 2011-08-06, Phil Steitz wrote: > >> On 8/5/11 9:40 PM, Stefan Bodewig wrote: >>> This means ZipArchiveOutputStream must decide whether it is going to use >>> the ZIP64 format before it knows whether it would actually need it or >>> not. If it signals i

Re: [compress] Need API Feedback/Advice for ZipArchiveOutputStream ans ZIP64

2011-08-06 Thread Stefan Bodewig
On 2011-08-06, Phil Steitz wrote: > On 8/5/11 9:40 PM, Stefan Bodewig wrote: >> This means ZipArchiveOutputStream must decide whether it is going to use >> the ZIP64 format before it knows whether it would actually need it or >> not. If it signals it is going to use ZIP64 then an implementation t

Re: [compress] Need API Feedback/Advice for ZipArchiveOutputStream ans ZIP64

2011-08-06 Thread Phil Steitz
On 8/5/11 9:40 PM, Stefan Bodewig wrote: > Hi, > > there are eight possible permutations of compressed/uncompressed entries > that get written to a seekable-/non-seekable stream whose size is either > known or unknown prior to writing them. > > One of them is prohibited (uncompressed/non-seekable/u

Re: [compress] Need API Feedback/Advice for ZipArchiveOutputStream ans ZIP64

2011-08-06 Thread Stefan Bodewig
On 2011-08-06, Torsten Curdt wrote: >> The only case that isn't covered so far is compressed / non-seekable >> output / input of unknown size. > WTF > How does the input stream distinguish between entry data and stream > data if the length is not know up front? The DEFLATE algorithm signals wh

Re: [compress] Need API Feedback/Advice for ZipArchiveOutputStream ans ZIP64

2011-08-06 Thread Torsten Curdt
> The only case that isn't covered so far is compressed / non-seekable > output / input of unknown size. WTF How does the input stream distinguish between entry data and stream data if the length is not know up front? cheers, Torsten -

[compress] Need API Feedback/Advice for ZipArchiveOutputStream ans ZIP64

2011-08-05 Thread Stefan Bodewig
Hi, there are eight possible permutations of compressed/uncompressed entries that get written to a seekable-/non-seekable stream whose size is either known or unknown prior to writing them. One of them is prohibited (uncompressed/non-seekable/unknown size) and has been prohibited before, no chang