>> 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: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
