Michael Bayne
b4dae3be33
moderately more sane progress indication. It's still non-ideal, because, for example, we'll start out assuming everything is length 1. So we'd have a queue like (1, 1, 1, 1). Then we start downloading the first resource and see that we actually have (1500000, 1, 1, 1), so we climb up to 99% downloading that first resource, and then we find out that we have (1500000, 450000, 1, 1) and we pop back down to 70% or so, and so on as we discover in turn that the web server lied to us about each file. The alternative is to just sit at 25% for ages, then sit at 50% for ages, then 75%, etc. Maybe that's better... I guess I just like to see some sort of smooth upward progress. This is only a problem for me since I'm hosting a Getdown client on Github which lies about Content-size in a HEAD request. So OOO projects will continue to give accurate progress reports.
What is it? ----------- Getdown (yes, it's the funky stuff) aims to provide a system for downloading and installing a collection of files on a user's machine and upgrading those files as needed. Though just any collection of files would do, Getdown is mainly intended for the distribution and maintenance of the collection of files that make up an application. See the Google Code project for documentation and other information: http://code.google.com/p/getdown Building -------- Getdown is built with Maven in the standard ways. Invoke the following commands, for fun and profit: % mvn compile # builds the classes % mvn test # builds and runs the unit tests % mvn package # builds and creates jar file % mvn install # builds, jars and installs in your local Maven repository