Author Topic: in memory ZipFile object via Inputstream  (Read 2366 times)

jyonkheel

  • Newbie
  • *
  • Posts: 1
    • View Profile
in memory ZipFile object via Inputstream
« on: April 05, 2016, 05:02:45 AM »
why InputStream? java allows insertion of BLOB objects, which allows me to put password protected zip files inside database, another is the jar embedded files which are obtained via Class.class.getResourceAsStream("/com/app/file.zip"); both these object are represented by a InputStream object, traditionally i would create a temporary directory and write the temporary files there before i could instantiate a ZipFile object, would it be possible to skip the temporary files step and just create an in memory ZipFile object in the future?  :) it would really be great and far more dynamic than making temporary file

Kingseason

  • Newbie
  • *
  • Posts: 2
    • View Profile
Re: in memory ZipFile object via Inputstream
« Reply #1 on: February 03, 2017, 08:57:43 AM »

It is information that is very useful to me. It is a very good thing that I have read it today.

 


Warning: Cannot modify header information - headers already sent in /home/content/66/5374066/html/zip4j/forum/Sources/Errors.php on line 346

Warning: Cannot modify header information - headers already sent in /home/content/66/5374066/html/zip4j/forum/Sources/Errors.php on line 347

Warning: Cannot modify header information - headers already sent in /home/content/66/5374066/html/zip4j/forum/Sources/Errors.php on line 348

Warning: Cannot modify header information - headers already sent in /home/content/66/5374066/html/zip4j/forum/Sources/Errors.php on line 351

Warning: Cannot modify header information - headers already sent in /home/content/66/5374066/html/zip4j/forum/Sources/Errors.php on line 352

Warning: Cannot modify header information - headers already sent in /home/content/66/5374066/html/zip4j/forum/Sources/Errors.php on line 353
Connection Problems

Connection Problems

Sorry, SMF was unable to connect to the database. This may be caused by the server being busy. Please try again later.