At a conference we are having a presentation on Filr and there seems to be some debate about the inability to have a modified file on a client pushed back to the server via Filr when Fils is configured to NOT sync everything to clients. Just because administrators have (probably correctly) prevented automatic sync of all user data to all users automatically should not prevent an individual file which is accessed, and modified, from being uploaded to the server when it is saved.
Pulling down files on-demand, and then having those files be editable, and then NOT uploading those files back to the server, seems like a great way to lose a lot of great data (in terms of the user's changes) and frustrate/lose customers quickly. If nothing else, Filr should detect this and throw up really big ugly messages that cannot be skipped since clearly the user wanted to make a change, clearly they did not copy the file somewhere else to keep track of it separately, and clearly they are no longer synchronized, so they are going to lose data.
by: Aaron B. | over a year ago | Other
Comments
I agree, although ideally the "do not sync" setting should not inhibit the upload of an individual edited file.