Home Documentation Tracker Download

What's new?

What's new in 0.9.8?

Compared to version 0.9.7, there are the following changes:

  • Enhancement: Updater must stop client's background process. (issue 51).

What's new in 0.9.7?

Compared to version 0.9.6, there are the following changes:

  • Enhancement: Basic LDAP support for WebDAV: It’s optionally possible to authenticate via LDAP - and then use a browser or other WebDAV-capable device to browse + read. Writing is not yet supported.

  • Enhancement: Many refactorings for improved extensibility (enhances code quality - not user experience) needed for downstream projects.

  • Bugfix: Fixed bug in collision handling happening in rare situations when a file type changed (e.g. from directory to ordinary file).

What's new in 0.9.6?

Compared to version 0.9.5, there are the following changes:

  • Bugfix: Fixed a bug concerning file (or directory) time-stamp reading/writing: With ext4, a file's time-stamp may have a resolution finer than 1 ms. This, however, was not handled correctly, causing a file (or directory) to be incorrectly resynced into the opposite direction. (issue 46).

  • Enhancement: Store repository alias inside repository (makes moving a repository-directory easier) (issue 18).

  • Enhancement: Retry in order to prevent "javax.net.ssl.SSLException: Received close_notify during handshake" when user waited too long (issue 27).

  • Enhancement: Resume same files after interruption (issue 34).

  • Enhancement: Resume faster after interruption by skipping all files that were already processed completely in the last, interrupted synchronisation run (issue 40).

  • Enhancement: Many refactorings for improved extensibility (enhances code quality - not user experience).

  • Enhancement: Renamed many classes for consistency reasons (enhances code quality - not user experience). Important: This breaks compatibility - you cannot use a 0.9.6 server with older clients or vice-versa.

What's new in 0.9.5?

Compared to version 0.9.4, there are the following changes:

  • Bugfix: Fixed a bug blocking the synchronisation, if the file name contained a '#' (issue 31).

  • Bugfix: Fixed a minor bug causing collisions when a file was modified locally while being uploaded (during re-down-sync) (issue 25).

What's new in 0.9.4?

Compared to version 0.9.3, there are the following changes:

  • Bugfix: Fixed a very bad bug causing more and more collision files to be created (issue 29).

  • Bugfix: Fixed a bug preventing CloudStore from creating repositories on Windows (issue 26).

  • Bugfix: Fixed a bug in Derby (which happened only very rarely) by switching to the new Derby version 10.10.2.0 (which was just released a few days ago) (issue 10).

  • Enhancement: There is now an automatic online-update (issue 24). Important: This online-update is enabled by default and will automatically update, whenever the command-line-program is used and a new version is available.

  • Enhancement: Introduced basic symlink support. Important: "Basic" support means that syncing a symlink is only possible, if both file systems support them! If one file system supports symlinks, but the other file system does not support them, the sync fails with an exception (if there is a symlink - if there is none in the repository, syncing still works fine, of course)! (issue 21).

What's new in 0.9.3?

Compared to version 0.9.2, there are the following changes:

  • Bugfix: Fixed dropRepoConnection sub-command (issue 16).

  • Bugfix: Fixed resource allocation leak causing the repos to stay locked (issue 17).

  • Enhancement: New inheritable configuration (issue 19).

  • Enhancement: Support multiple different file-write-stategies and switch to the default strategy directAfterTransfer (issue 19).

  • Enhancement: Improve security by switching to TLS 1.2 (issue 20).

What's new in 0.9.2?

Compared to version 0.9.1, there are the following changes:

  • Bugfix: File/directory names containing both curly braces - '{', '}' - and spaces caused exceptions (issue 14). We changed the way path elements are encoded to fix this issue.

  • Enhancement: Improved Upstart configuration and added System IV start/stop script to run CloudStore server as a service (a.k.a. daemon) on GNU/Linux systems (issue 11).

  • Enhancement: New commands for adding and dropping repository aliases (issue 13).

  • Enhancement: More javadoc.

Version 0.9.2 is fully compatible with version 0.9.1. Upgrading (and even downgrading) is therefore possible without any special care. It is, however, recommended to use the same version everywhere (on all clients and all servers).

What's new in 0.9.1?

Compared to version 0.9.0, there are the following changes:

  • Enhancement: Huge performance improvement with very large repositories (more than 100 thousand files). It turned out that Derby is pretty slow with a composite primary key (2 long fields modelling a UUID) when there are about 1 million records in a table. This happened in a test environment with many small redundant files (causing nearly one million CopyModification instances to be persisted). The UUID was thus replaced by an ordinary single field PK of type long.

    Important: The new database version (2) is not compatible with the old one (1) anymore! There is no automatic upgrade! Please remove the .cloudstore-repo directory in every repository manually and re-create it! We consider 0.9.* to be experimental and don't think that anyone (except for the developers) is already using it.

    So please let us know, if you already require an automatic upgrade of the repositories.

  • Enhancement: The new copy/rename/move detection makes sure a file is not copied across the network unnecessarily.

  • Enhancement: Faster sync especially when suffering high latencies due to multi-threaded transfers.

  • Enhancement: Improved security by preventing denial of service attacks by limiting pending connection requests and by cleaning up expired requests.

  • More enhancements and bug fixes.

Documentation
About
Releases