Re: CPIO archives

Also please note that it won't write to the filesystem if the rpm that 
is being read is constructed from a File..

It's only in the case of using only an inputstream where he will do so.

some thoughts about this:

- We could have an "read and extract immediately" function, which would 
use same inputstream without saving to disk.

- We could allow to set a "treshold" size, where it would keep it in 
memory if smaller than that size, or use disk if bigger.

Michael Kuß wrote:

>Hi Yannick,
>
>I have some suggestions (no offence intended) regarding the cpio handling:
>
>1. the CPIOPayloadArchive should read the data from an InputStream or
>   DataInputStream, so that a rpm file can be read continuously.
>2. The CPIOPayloadArchive should not write to the disk unasked. So the
>   the data should be held in memory. It would help to make some actions
>   faster (e.g. list of all files, calculate signatures, ...)
>3. We should use BufferedInputStream wherever an InputStream is initialized.
>   I have tested on a large rpm file (ca. 70 MB) and it was very slow.
>
>I can do some work there but I don't want to conflict with your changes.
>
>I have also played with the idea to include a text formatter for the
>datatypes so
>that displaying these can be configured. But at the moment I have no good
>idea
>how to solve this.
>
>And there is also the regular work to do. Like cleaning up the flat *sigh*.
>
>Greets,
>   Micha
>
>  
>




-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive?  Does it
help you create better code?  SHARE THE LOVE, and help us help
YOU!  Click Here: http://sourceforge.net/donate/