Problem:
Let's say you have a central server which has your files and documents. This is at home. Now, you also have flash drives and other external storage stuff. While you were away from home, you worked on one of your files, and now you want to update the central server with that file. But you don't want to replace or delete anything because someone else may have modified the central server file also while you were gone. So how can the server always hold the latest file, but also safeguard against deletions or accidental updating.
At first, I would just say to compare timestamps and use the latest one. but there could be the situation where the file in question was modified separately by two different users. So the timestamp wouldn't necessarily really be sufficient. Also, I'm not looking to somehow merge the data from two sources back into one file, that's too complicated for my needs. All I want to do is make sure nothing gets deleted or overwritten.
So I'm trying to figure out the logic of how to have the current file be the latest version, but also not overwrite or delete anything and have the alternate or backup versions stored somewhere else just in case. I'm planning on doing this mainly with a program like Super Flexible File Synchronizer, since it has lots of options for monitoring folders, versioning, and moving things around like this.
I'm curious about your thoughts on this. It's essentially a low-level solution to the multi-user, live collaboration problem. But since there isn't any live collaboration (multiple people editing a file at once), it's more of a synchronizing problem. I'm also trying to avoid services like dropbox and such. These transfers and connections will be direct: either directly connecting to the folders through the network, or sticking in a usb drive.
Let's say you have a central server which has your files and documents. This is at home. Now, you also have flash drives and other external storage stuff. While you were away from home, you worked on one of your files, and now you want to update the central server with that file. But you don't want to replace or delete anything because someone else may have modified the central server file also while you were gone. So how can the server always hold the latest file, but also safeguard against deletions or accidental updating.
At first, I would just say to compare timestamps and use the latest one. but there could be the situation where the file in question was modified separately by two different users. So the timestamp wouldn't necessarily really be sufficient. Also, I'm not looking to somehow merge the data from two sources back into one file, that's too complicated for my needs. All I want to do is make sure nothing gets deleted or overwritten.
So I'm trying to figure out the logic of how to have the current file be the latest version, but also not overwrite or delete anything and have the alternate or backup versions stored somewhere else just in case. I'm planning on doing this mainly with a program like Super Flexible File Synchronizer, since it has lots of options for monitoring folders, versioning, and moving things around like this.
I'm curious about your thoughts on this. It's essentially a low-level solution to the multi-user, live collaboration problem. But since there isn't any live collaboration (multiple people editing a file at once), it's more of a synchronizing problem. I'm also trying to avoid services like dropbox and such. These transfers and connections will be direct: either directly connecting to the folders through the network, or sticking in a usb drive.
















- carpe noctem
...How do you flail and cover your eyes at the same time?