Re^2: Distributed agreement woes

Replies are listed 'Best First'.
Re^3: Distributed agreement woes by ikegami (Patriarch) on Jul 02, 2010 at 22:41 UTC
No, I didn't. Your requirement states some script wants to know if all machines are in sync. Therefore, you have a requester. That's all my method requires.	[reply]
Re^4: Distributed agreement woes by andrew732 (Novice) on Jul 02, 2010 at 22:49 UTC
But how does a local host know that all remote hosts have completed making their local copies of the file? Sleep until the file exists on the other host and then make sure no other host has a lock on the file? That's the kind of stuff that I don't want to code myself, especially because I need guarantees that race conditions won't arise. It's very possible that I'm overthinking all this; I was kind of just hoping someone would say something like "oh yeah, just use distributed_agreement.pm" from cpan or something like that.	[reply]
Re^5: Distributed agreement woes by NetWallah (Canon) on Jul 03, 2010 at 00:13 UTC
If this is like a version control application, git may be an answer - it is distributed, supports replication, and has notification on update. You may be able to plagiarize parts of it to build your system. Syntactic sugar causes cancer of the semicolon. --Alan Perlis	[reply]
Re^5: Distributed agreement woes by ikegami (Patriarch) on Jul 03, 2010 at 00:21 UTC
But how does a local host know that all remote hosts have completed making their local copies of the file? A non-existent file is different than an existent file. Are your specs incorrect?	[reply]