Hi Chris,

I was thinking that something like
Compress.getInstance(String compressorType);
like Crypto would be nice.
This way you can get a unique "entry point" for every compression algorithm 
that can provide its own methods to compress/decompress/add files etc etc.

Bye
Piero

Alle 10:58, martedì 14 febbraio 2006, C. Grobmeier ha scritto:
> Hello,
>
> not knowing how to start best, i would like to kick off an discussion
> about the goals of [compress]. As i wrote in an email before ages, i
> have allready started to check out the existing lib and want to see this
> component working.
>
> I noticed, that compress ist divided into three different APIs, one for
> every compression algorithm: Zip, BZip2, Tar.
> Every implementation is not complete and cool features are not ready yet
> (f.e. no possibility to delete single files from a zipfile).
>
> Next problem is the lack of a commonly used interface: it seems one have
> to learn everything about the 3 components to use it. This is quite
> uncomfortable.
>
> I think it would be very best to have one interface, say Compress.class.
> This could organize the Compression itself.
>
> Here are the keypoints. Compress should be used to:
>
>       - load or create an existing compressed file,
>       - add files to compressed file,
>       - compress a file,
>       - return a list of stored files
>       - delete a single file from the compressed file
>       - in a later release: set special fields, like zip-fields
>
> For these actions, Compress uses one of the 3 Compressors,
> ZipCompressor, TarCompressor or BZip2Compressor which are beeing loaded
> lazily.
>
> This is, how i would like to see the compress package. I think before
> fixing and extending the old apis, it makes sense to discuss the
> direction in general.
>
> Ok, as a newbie to apache contributing all your comments and tips are
> welcome.
>
> Cheers,
> Chris
>
>
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]

-- 
GPG KeyID: 84AE988E
Fingerprint: F0A0 CA2A 8D8F CC12 3F5E  C04C D8D5 9DC3 84AE 988E
gpg --keyserver x-hkp://search.keyserver.net:11371 --recv-key 84AE988E

Attachment: pgpLMCCbnjynZ.pgp
Description: PGP signature

Reply via email to