51 ms·
Unfortunately zsync is a bit old and needs some updates for modern HTTP (doesn't support HTTPS, hand-written C HTTP client. We had to patch the header parsing a
by kbaker 5y ago
Unfortunately zsync is a bit old and needs some updates for modern HTTP (doesn't support HTTPS, hand-written C HTTP client. We had to patch the header parsing and mime handling to get it to be compatible with our test server...)
If it swapped to libcurl as a backend, it would be much more flexible and stay up-to-date, since the idea is solid. That being said there are many spiritual successors to look into:
- zchunk
- casync
- desync
- bita
- traceroute66 5y ago> Unfortunately zsync is a bit old Yup. Last update of the Github repo was 2015. zsync is effectively abandonware.
- dividuum 5y ago> If it swapped to libcurl as a backend [..] There's https://github.com/probonopd/zsync-curl https://github.com/probonopd/zsync-curl. Seem pretty active. So there's hope.
- bruce_one 5y agoI believe probonopd is maintaining that fork as part of their work on AppImage - so it does have an active user group, which is great. (The AppImage docs suggest using zsync as a mechanism for making images updateable: https://docs.appimage.org/packaging-guide/optional/updates.html https://docs.appimage.org/packaging-guide/optional/updates.h...)