1.1.0 Release Notes

The major new feature of the 1.1 experimental branch is static ranges. If a client is assigned a static range, the server will always assume that the client is able to serve files from that range without tracking the files individually. Instead of being pre-distributed, if a file isn't currently cached, the client will proxy-request it from the image servers on-demand, then store it for later use.

Static ranges will only be assigned to faster clients that have a proven track record, and only if it has enough disk space set aside to store all the files for the static range - in other words, 1/65536th of all hosted images. Currently, the minimum requirement is 500 MB disk space per assigned range. A client can be assigned an arbitrary number of ranges depending on its capabilities.

Files in a static range will not be tracked by the server, nor will the client bug the server about it when it adds the file or in the unlikely case it decides to delete it. This should greatly reduce the server-side load of tracking clients. It will also allow us to greatly increase the file coverage per region.

This version of H@H will eventually be able to make advantage of a lot more disk space than before. So if you have loads of it just laying around, it doesn't hurt to bump it up a bit.

- Core: Support for static ranges was added.

- Core: The client will no longer terminate if it fails to set socket buffer sizes for any reason.

- Core: Some platforms didn't like the argument order we used for ping, so this was switched around.

- Core: Added user friendly interpretations for a few missing startup errors.

- Core: The stale file pruning mechanism will no longer run if the server hasn't been reachable lately.

- Core: HTTPServer should now recognize IPv6 localhost and private network ranges.

- Core: Removed support for pre-1.0.4 URL format.

- Core: The --use-more-memory mode is now the default. If this causes issues, you can revert to the old behavior with the new --use-less-memory flag.
-- Unless you have physical memory limitations, if you run into Out of Memory errors, you should try using -Xmx1g flag first, which will increase the maximum Java heap space to 1GB.

- Core: Fixed logging could throw a NullPointerException if a null somehow ended up in the final print.

- GUI: Workaround for Java 7 randomly failing to return the underlying text of the logging pane when using RDP.

- Downloader: Fixed cutoff for overly long filenames not being applied correctly. (Some poorly written operating systems fail the final file copy operation when total path length exceeds 255 characters.)


As the 1.1 branch is considered Beta, it's not added to the H@H client page. Download it here:

Runnable
Source