in reply to Best practices for file synchronization? (Mod time vs. contents compare)

I wrote something just based on modification time and file size. I was comparing (over 2500) files over (slow) VPN, so I didn't want to read the file if I didn't have to, and even avoided perl's -X file test operators because it was slow to test every file. Instead I used Win32 API functions.
  • Comment on Re: Best practices for file synchronization? (Mod time vs. contents compare)

Replies are listed 'Best First'.
Re^2: Best practices for file synchronization? (Mod time vs. contents compare)
by OfficeLinebacker (Chaplain) on Jun 12, 2006 at 18:44 UTC
    runrig++! This is exactly what I am doing (replacement for Briefcase!)

    I'm going to give benchamarking MD5 vs File::Compare a try, and then look into your solution!

    _________________________________________________________________________________

    I like computer programming because it's like Legos for the mind.

[reply]
Re^2: Best practices for file synchronization? (Mod time vs. contents compare)
by OfficeLinebacker (Chaplain) on Jun 12, 2006 at 19:48 UTC
    Argh, Win32::API not present on the desktops. I'll be posting benchmarks on the other ways of doing it in a bit.

    _________________________________________________________________________________

    I like computer programming because it's like Legos for the mind.

[reply]
      Win32::API doesn't come with the standard install of ActiveState Perl, but it is easily installed with the ppm utility.
[reply]

In Section Seekers of Perl Wisdom