On 18.05.2007, at 19:17, Bear Giles wrote:
Torsten Curdt wrote:
Hm... seems like I disagree here. I want a simple library that
deals with common compression and archive formats
- tar
- ar
- cpio
- gzip
- bzip2
- zip
VFS is a filesystem abstraction layer. It may use the
library
On 18.05.2007, at 05:13, Bear Giles wrote:
Thorbjørn Ravn Andersen wrote:
I therefore suggest that the tar methods should be migrated to the
vfs module (if suitable) and that the compress module should
contain methods that can compress/uncompress streams (which is
easily extendable to
On 5/18/07, Torsten Curdt [EMAIL PROTECTED] wrote:
VFS is a filesystem abstraction layer. It may use the library but
should not provide the implementation IMO.
+1, compression is a rather important topic in itself.
--
My cats know that I am a loser who goes out for hunting every day
Torsten Curdt wrote:
Hm... seems like I disagree here. I want a simple library that deals
with common compression and archive formats
- tar
- ar
- cpio
- gzip
- bzip2
- zip
VFS is a filesystem abstraction layer. It may use the library but
should not provide the implementation IMO.
[EMAIL PROTECTED] skrev den 17-05-2007 00:20:
You can't do that if you only see archives as boring things used in
backups. Backups that are either windows (zip) or unix (tar), yawn.
If you go hardcore, you'll notice that a lot of common file formats
provide support for arbitrary data to be
Thorbjørn Ravn Andersen wrote:
I therefore suggest that the tar methods should be migrated to the vfs
module (if suitable) and that the compress module should contain
methods that can compress/uncompress streams (which is easily
extendable to files, http connections etc).
By doing so there
Hi!
I agree that the 'compress' tar classes should be removed and a
pointer left to the VFS project.
We've already moved an early version (before the api cleanup) of the
COMPRESS codebase to VFS.
The thing is, that VFS normally would NOT like to provide the
implementation for a certain
On 5/15/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
I'm interested in merging some earlier archival work (in C) into commons
compress and would like to know who to coordinate with. The changes will
be... substantial... and I'll probably just fork the project for now, with
a goal of merging
On 5/15/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
I'm interested in merging some earlier archival work (in C) into commons
compress and would like to know who to coordinate with. The changes
will
be... substantial... and I'll probably just fork the project for now,
with
a goal of
Torsten Curdt wrote:
On 15.05.2007, at 23:29, [EMAIL PROTECTED] wrote:
I'm interested in merging some earlier archival work (in C) into commons
compress and would like to know who to coordinate with. The changes
will
be... substantial... and I'll probably just fork the project for now,
On 5/16/07, Bear Giles [EMAIL PROTECTED] wrote:
Torsten Curdt wrote:
On 15.05.2007, at 23:29, [EMAIL PROTECTED] wrote:
I'm interested in merging some earlier archival work (in C) into commons
compress and would like to know who to coordinate with. The changes
will
be... substantial...
I'm interested in merging some earlier archival work (in C) into commons
compress and would like to know who to coordinate with. The changes will
be... substantial... and I'll probably just fork the project for now, with
a goal of merging in late summer.
Also, what version of the JDK do
12 matches
Mail list logo
