In your specific situation, I would suggest creating something called a symbolic link. You will have to do the following from the Terminal:
- Open Terminal
- Type: cd ~/Desktop
- Type: ln -s /path/to/folder/ NAME
It will show up on your desktop and look like a regular alias, but it is not.
Adding an example:
ln -s ~/Dropbox ~/Desktop/Dropbox
This will create a symbolic link on your desktop called "Dropbox" pointing to the /Users/YOURUSERNAME/Dropbox folder.
I don't know the technicalities of this, but I do have the situation where I and my assistant operate a common dropbox with two different computers going on and off at different times.
The answer to your question is that when you connect with the Cloud, Dropbox knows (somehow) that the version currently on the Cloud was originally synced from your computer. So if your computer version is different, that is the version that will be synced to the Cloud.
If two computers (say A and B) are using the same dropbox, and each make changes offline, then the first computer powers up (let's say it is computer A) will generate a sync of its update to the cloud. So now there will be same version (containing the A update) on A and Cloud.
When computer B is powered up, Dropbox will realise that computer B's version of the file is not only different from the current cloud version (which is normal) but different from the last time Dropbox synced from it. So if it were to sync B's file to the A version, B's changes would be lost. So what Dropbox does is make a copy of the B version and add "B's conflicted file" to the file name. B's original file is then synced to the A updates. The conflicted file, containing the B updates, is then synced to the cloud and back down to A.
Deletions, and conflicts arising from selective sync, are handled in a similar way
A conflict also arises if one of the computers does not close the file before powering down. Syncing does not occur on an open file, so in this case B's updates will be the ones that are synced, and A's open file will end up as a conflict. This can be a huge pain to harmonize, but this is our fault, not Dropbox's.
Hope this helps.
Best Answer
You could move the cache by going into the FF config page. Type about:config in the address bar and click the warning button. Right click somewhere on the about:config page and select New string in the context menu. In the first dialog box type browser.cache.disk.parent_directory and click OK. In the next box type the folder where you want to store your cache, e. g. c:\ (FF places the cache folder under the path you enter, in this example the cache folder would be c:\cache). Now you can sync to Dropbox without having to sync the cache folder. It is strange though that your cache folder isn't under Appdata\Local where it should be. Using my above method you could force it to be placed there.