This is a maintenance release which mainly aims to correct most of the issues with the client randomly terminating when it fails to connect to the server in certain ways. It also fixes some other minor problems, like the cache handler not deleting files at boot if the size of the cache has been reduced, and the used cache size is larger than the new maximum cache size.
Two new servers have now been installed and added to the server pool for Galleries, to handle the image lookup part of the system. This should greatly increase the overall performance both of image browsing and most other things, since it frees up plenty of resources on the primary database server.
Also, since we now have sufficient capacity, the image browsing limit has been increased to its original level.
Post here if you encounter any problems with the new configuration.
- The reorderer has finally been rewritten so that it works properly on large galleries. What used to take 5 minutes on the old one should take 0.5 seconds on this one, and it should no longer choke on very large galleries. It'll probably support the current system maximum of 10000 images for a gallery without too much trouble if you have enough RAM, though I haven't tested quite that high. Note that for particularly slow computers, you can append &nofancy=1 to the URL to make it stop moving things around in real-time.
- Support has been added for the new Hentai@Home proxy system added in H@H 0.3.0.
Bug fixes
Quick Browse had some issues with retaining the width and height of the first loaded image and applying them to other images as well. This usually wouldn't have been a problem for most galleries, but still, fixed.
Hentai@Home 0.3.0
Proxy support, but not the kind you think
Support has been added to have Hentai@Home act as an image proxy on behalf of people browsing E-Hentai Galleries. If a proxy has been configured under My Settings on EHG, all requests for images will be piped through the set Hentai@Home client instead of going to the server. The Hentai@Home client will then see if the image is available from its cache; if it is, the file will be loaded without involving the server, and if not, Hentai@Home will retrieve the file from the server on behalf of the browser, storing the image in its cache in the process.
What does this mean? For one, whenever you browse an image, the image will be cached, allowing other people to download it from you, thus greatly increasing the distribution effect. Furthermore, provided your cache doesn't run full, no images will be downloaded more than twice, making them instantly available (and not counting against any image loading limits) after viewing it the first time. Finally, since Hentai@Home knows how large the file is supposed to be, it will automatically retry any failed or corrupted images without even being asked.
Note that in the default configuration, H@H runs as a semi-closed proxy, that is, it will only accept proxy requests from localhost and private network addresses. It is possible to disable it fully or run it as an open proxy. Contact me if you wish to change this. (No, the configuration page isn't done yet.)
Other stuff
- The way the client builds and sends cache data and speedtest data to the server has been rewritten to decrease startup memory usage, since this is usually not released afterwards.
- The throttle was not doing its job properly when several connections were active at the same time. It should now do a much better job obeying the speed limit. Note that this would not have affected bandwidth usage over time.
- Fixed a rare bug where HTTP sessions would get stuck in a limbo, with the client trying and failing to reset them every 10 seconds.
The download is available in the usual formats: ziprartar.gz (right-click and save as)
