It's not like Rsync. If you were to try a byte and byte comparison between what you have on your PC versus what you have on your computer it would take hours to get an update.
In fact, when Impulse v1.0 first came out, it was doing some (not a lot but some) byte by byte checking to do a sync lik eyou describe and it took 40 minutes on average to do the comparison ("preparing") which is one of the reasons why so many people here got a negative first impression of Impulse.
If you think about the thousands of files involved and the fact we can drop a few files into a directory and Impulse just figures it out and does for, for the user in seconds, it's a no brainer. Especially when you spread it across hundreds of other programs -- not just Sins but GalCiv, Demigod, WindowBlinds, Object Desktop, etc.
Hi Frogboy, Yes, after digging around, it makes sense to put the stuff into an XML and then check CRCs or such for changes and then copy the relevant stuff over. Yes, I agree, you guys got it right.. this is the right way to go as opposed to rsync specifically..
But I'm still curious as to how Impulse (and the developers) handle settings. For example, let us say I have a new INI name/value pair (alt. substitute with registry/etc/or even a new INI file) that needs to be included for say a new feature - maybe a user configurable setting, I guess I'm asking if that is the responsibility of sins.exe (as Blair mentioned game specific settings), or does Impulse help to do that?
I ask because this topic is about the benefits of Impulse distribution.. so if Impulse is a delivery system, would it make sense to use other tools (on top of, together with, etc) to handle the installer/upgrades/patching - for example NSIS? Sounds like a dumb question, I know.. sorry if it is 