Splitting and compression

  3 posts   Feedicon  
Replies: 2 - Last Post: June 11, 2009 14:19
by: Glenn Brunette
« Older Topic » Newer Topic
showing 1 - 3 of 3
 
Posted: June 09, 2009 20:54 by Glenn Brunette
Looking to add support for compression and also splitting/reassembly, and while this is not hard to do, I keep hitting a wall in terms of balancing functionality vs. freedom. I can do some nice tricks to automate the compression, encryption and split (and the reassemble, decrypt, and decompress), but it means that I will need to specify the name of the remote file stored in the cloud. This is good for simplicity but bad if you want to be able to have your own file names.

Also, should encryption always be enabled? What about compression (before encryption)? Do you want to specify your own maximum size (as it relates to splits?)

So many choices so little time. Send me your feedback!
 
Posted: June 11, 2009 10:17 by Peter
You need to compress BEFORE you encrypt, since compressing already encrypted data is significantly less beneficial.

I'm not sure why your splitting, an explanation of the reason would be useful.

I think you probably need to find a way to abstract the actual file names from the file objects themselves, otherwise you'll keep hitting walls.

The project is cool & the proposition is sound.


 
Posted: June 11, 2009 14:19 by Glenn Brunette
Peter,

Thank you for sharing your feedback!

As far as compression, yes, that was the plan and in fact is now implemented in version 0.4 of the code available from the Downloads link. I had used the parenthetical in my original post to advise people that I was doing compression before encryption (for exactly the reason you pointed out).

As far as splitting, Amazon's S3 has a maximum file size limit of around 5 GB. I have spoken with people for whom this is a real problem. The goal was to make it easy for people to use the tool regardless of the size of the file they want to send to/retrieve from the Cloud storage provider. When enabled, splitting will break up files into chunks based upon a maximum file size limit (default is 4 GB but you can change the default with a command line option). You are correct about file name issues, although I have taken an optimization of using a pre-defined (and documented) suffix. You can find more information about this in my blog posting at: http://blogs.sun.com/gbrunett/entry/new_cloud_safety_box_v0.

Again, thank you for sharing your feedback! It is very much appreciated!

Take care,
Glenn
Replies: 2 - Last Post: June 11, 2009 14:19
by: Glenn Brunette
« Older Topic » Newer Topic
  • Mysql
  • Glassfish
  • Jruby
  • Rails
  • Nblogo
Terms of Use; Privacy Policy;
© 2010, Oracle Corporation and/or its affiliates
(revision 20120518.3c65429)
 
 
Close
loading
Please Confirm
Close