Wait, I thought by the subject line and subsequent ending sentence, he wanted the best way to do this, not specifically make it on his own for the purpose of making it. My apologies if that's the case. Sure, the list follows: Are you going to use encryption for the data? If so, what algorithm? Are you going to use compression? If so, are you going to change the streaming compression for different file types E.G. text compresses very well with lzma 2; however, I wouldn't even bother doing it on h264 video files. Are you going to do remote differentials, then compare results? If you're going to do diffs, what are you going to use? Crc? Md5? Sha? Binary diff algos like the recent modification to diff from Google? What happens when a transfer is interrupted? Is the system always guaranteed a safe state if this happens? What is your conflict resolution strategy? File x exists on both servers but with the same timestamp and different hash values or file sizes, if you're going super simplistic, what do you do? There are many other conflicts in this vane. Why are you using a different protocol than one natively available on Windows, and almost ubiquitously available on Linux E.G. samba. Speaking of samba, have you considered traffic chattiness? The back and forth could kill your performance. Is security a concern? File access can get very tricky very fast, so are outside users going to use this, or could they potentially do so? Speaking of security, how are you handling authentication? What's the production guarantee of this software. This means, are you wanting this thing to be up, no matter what? If so, what steps are necessary to make that happen ... Is this being used for backups of some kind, and if so, how often will you test to make sure files can transfer the other way? Speaking of files ... There are issues when going cross platform such as permissions and other file system specific bits. Are these bits, permissions, and ownership information, as well as metadata, going to be preserved? I didn't count them, but ... There you go. That was only a few moments of typing, so I'm sure there are other questions as well. If you're designing this for the heck of it, then good luck: it sounds like a super fun project. Sorry again. I thought you wanted an existing solution. Take care, Sina -----Original Message----- From: programmingblind-bounce@xxxxxxxxxxxxx [mailto:programmingblind-bounce@xxxxxxxxxxxxx] On Behalf Of David Engebretson Jr. Sent: Wednesday, October 06, 2010 11:28 AM To: programmingblind@xxxxxxxxxxxxx Subject: Re: If This Can Be Done, How? Hi Sina, Could you expand on your thoughts? You said there were 10 or 20 things Jim hadn't thought of. I'd like to see a list of those... I'll bet he would as well. I'm guessing, since he is trying to create the tool on his own, he wants to gleam the knowledge of creating said software. It's nice to have this list to bounce ideas off of people who are more knowledgable than us, a? Cheers, D __________ View the list's information and change your settings at //www.freelists.org/list/programmingblind __________ View the list's information and change your settings at //www.freelists.org/list/programmingblind