commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Torsten Curdt <>
Subject Re: [compress] release 1.1?
Date Wed, 21 Jul 2010 21:38:12 GMT
>> Especially as there should be a limit of what you can expect/express.
>> After all it describes a file with it's metadata. In theory
>> ArchiveEntry could be the superset of all that's there. Looking at the
>> various implementations this doesn't seem to be too far fetched. If a
>> particular ArchiveEntry doesn't support e.g. getGroup() it would just
>> return null ...but I am a little back and forth on this. Mostly
>> because of methods returning primitives ...and the bloat of the
>> interface.
> ArchiveEntry.getGroup() returning null - how many different option
> would we implement which would return null - sometimes.
> What about ArchiveEntry.setOptions( Map options) and
> Map ArchiveEntry.getOptions?

A Map is the most flexible way ...but I am not sure we really need
that flexibility.
The entry attributes are really not that diverse. Seems most archives support
Unix style attributes. We probably should do a union and see how they differ
across the archive implementations to make a call here.

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

View raw message