ifolder is a great solution but it lacks stability.

i) client

the client is very heavy (3.8,3.7) and very slow. there are some situations when ifolder is not synchronizing recently. unfortunately there is no logic behind this. server files are ok, client 1 is missing one part, client 2 another part. mostly it is not possible to restart the sync without deleting the whole local directory.

ii) administration

it is not very obvious how ifolder is managing the files and the file system (data store). you can define more than one data store but what will really happen? how are the files moved from one store to the other, you sometimes will have two (or n) similar physical directory structures. when the client fails syncing the administrator is not able to find out what really went wrong and which files didn't sync correctly. she is also unable to restart the sync process or define a "new epoch" for these files manually.

iii) consistency

what happens if you delete or move a file in the data store of the ifolder server? a situation you can run into when using antivirus solutions, or perhabs an os crash. trying out shows inconsistencies in the ifolder database, because the non existing file is still referenced in the database.  not enough that this can happen, where are the administrative reorg tools to solve this?

ifolder has been great for years and has been a very early solution. unfortunately development is extremly slow. meanwhile there are some alternatives doing a good (better?) job. you have to be a bit faster in development with a bit more focus on your users or customers --- companies.

ja