Hi Carl! Yep, einst...@home is still using the boinc_zip code on the client side (for our standard application). On the server side (validator) we are using zlib and zziplib. For our most recent application, however, we are using the gzip compression of the Core Client and have no compression implemented in the application itself, which I find the better and more general approach.
As for bzip2 and z7 note that the better compression rate is bought with a much longer compression time compared to e.g. gnuzip. Not sure if this is worth the deal, especially on slower CPUs. Best, Bernd Carl Christensen wrote, On 7/20/09 11:42 PM: > Hi, > > I'm looking at replacing boinc_zip for various reasons, mainly it's been a > kludge of two libraries which are old & complicated to update, and thinking > of moving to something like the bzip2 lib (which also compresses better). > > as far as I know it's just CPDN, QCN, Rosetta, and Einstein that use it? and > I think Einstein had some extra code for validating a zip file? So I would > like to get some feedback on doing away with boinc_zip and replacing it with > a better underlying compression routine. This would be done over a few > months to 6 months -- as I'm going back to CPDN & juggling working on that & > QCN, so won't have much time. > > Or I'd be happy if someone else is interested in porting my boinc_zip wrapper > with an underlying compression routine such as bzip2 or whatever is in vogue > & secure these days! > > > > > _______________________________________________ > boinc_projects mailing list > [email protected] > http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_projects > To unsubscribe, visit the above URL and > (near bottom of page) enter your email address. > _______________________________________________ boinc_dev mailing list [email protected] http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev To unsubscribe, visit the above URL and (near bottom of page) enter your email address.
