commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Stefan Bodewig <>
Subject [compress] Do we want formats without write support (Unix dump, maybe RAR)?
Date Tue, 09 Aug 2011 03:25:02 GMT

in JIRA Bear Giles has provided an ArchiveInputStream implementation for
the Unix dump format.  AFAIU writing an output stream would be quite
difficult in particular since the format requires information not
available to Java and the road to JNI/JNA doesn't look like one I'd like
to take right now.

But read-only support could still be useful for some users.

The RAR format is in the same boat for a different reason.  The format
itself is not fully documented but a Java library exists to read RAR
archives and its license - which explicitly prohibits using the code
base to reverse-engineer write support - is listed as Category B
<> [1]

So what is the feeling in general, are read-only formats OK or do we
want to only support formats that we can write as well?


[1] The link to the license is dead and some searching around indicates
Sourceforge has kicked out the project because of its license.  The new
home seems to be (according to Ohloh)
<> and a different fork by Jukka
Zitting - for use inside Apache Tika - exists as well at github.

So far I have no idea how feasible an InputStream implementation based on
the codebase would be.

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message