Re: [compress] ZIP64: API imposed limits vs limits of the format

2011-08-05 Thread Stefan Bodewig
On 2011-08-04, Torsten Curdt wrote: >> ZipFile relies on RandomAccessFile so any archive can't be bigger than >> the maximum size supported by RandomAccessFile.  In particular the seek >> method expects a long as argument so the hard limit would be an archive >> size of 2^63-1 bytes.  In practice

Re: [compress] ZIP64: API imposed limits vs limits of the format

2011-08-05 Thread Stefan Bodewig
On 2011-08-04, Lasse Collin wrote: > On 2011-08-04 Stefan Bodewig wrote: >> There are a few places where our implementation doesn't allow for the >> full range the ZIP format would support. Some are easy to fix, some >> hard and I'm asking for feedback whether you consider it worth the >> effort

Re: [compress] ZIP64: API imposed limits vs limits of the format

2011-08-04 Thread Lasse Collin
On 2011-08-04 Stefan Bodewig wrote: > There are a few places where our implementation doesn't allow for the > full range the ZIP format would support. Some are easy to fix, some > hard and I'm asking for feedback whether you consider it worth the > effort to fix them at all. I guess that these ar

Re: [compress] ZIP64: API imposed limits vs limits of the format

2011-08-04 Thread Torsten Curdt
> ZipFile relies on RandomAccessFile so any archive can't be bigger than > the maximum size supported by RandomAccessFile.  In particular the seek > method expects a long as argument so the hard limit would be an archive > size of 2^63-1 bytes.  In practice I expect RandomAccessFile to not > suppor

[compress] ZIP64: API imposed limits vs limits of the format

2011-08-04 Thread Stefan Bodewig
Hi all, ZIP64 support in trunk is almost complete except for a case that is pretty easy to implement but where I'll ask for API feedback once I've managed to read up on how the InfoZIP people handle it. There are a few places where our implementation doesn't allow for the full range the ZIP forma