Looking through the protocol, I can’t tell if when you have edited a file, it sends the whole file again, or just the blocks that contain the delta. The latter would be huge in regards to performance.
I have tried it briefly. One limitation I see is that you cannot have several directories that you sync, only one. But they might change that in a newer version?
Incidentally, the limitation to sync only one folder was considered a accidental great feature for Dropbox. They originally shipped it as such because they wanted to get the product out. Turns out the simplicity was great for adoption.
I’m a little unclear on how this works. Is the code in the repo both a client and a server? I’m assuming that all nodes will need to run an instance and somehow they get wired up through the web interface. Is that right?
Looking through the protocol, I can’t tell if when you have edited a file, it sends the whole file again, or just the blocks that contain the delta. The latter would be huge in regards to performance.
I added a big file (188MB) and changed some bytes in it. The change propagated really quickly on a slow connection. I suppose they only update blocks.
This looks really interesting. Anyone here tried it?
I have tried it briefly. One limitation I see is that you cannot have several directories that you sync, only one. But they might change that in a newer version?
Incidentally, the limitation to sync only one folder was considered a accidental great feature for Dropbox. They originally shipped it as such because they wanted to get the product out. Turns out the simplicity was great for adoption.
I’m a little unclear on how this works. Is the code in the repo both a client and a server? I’m assuming that all nodes will need to run an instance and somehow they get wired up through the web interface. Is that right?
Seems like it’s server and client. I had to add each node to each other node to get it to sync files.