On Fri, Mar 27, 2009 at 1:46 PM, Edward K. Ream <[email protected]> wrote:
> This is a much harder question. I've been daydreaming about what the > real issues are. Some preliminary thoughts: > > 1. Each private file will contain timestamp and checksum information > about itself and the corresponding public file. By definition, the Timestamp is very fragile, checksum is the safe & correct way to go. > users, so the sky is the limit. It may also turn out to be useful to > have a single timestamp/checksum line at the start of *public* files. Contents of public file in itself gives the checksum. > We can use this information to detect out-of sync conditions. Again, checksum is different => we are out of sync. It's that simple. > not in possession of enough data to make a reasonable choice. Out-of- > synch warning dialogs can *never* be a design option. If they are > required, the whole scheme fails. Period. Being out of sync will just revert to @auto import. > 4. Happily, bzr is written in Python, so it is conceivable to hack bzr > to aid Leo updates. OTOH, this probably would not be tolerated in non- No need to hack bzr, it's possible to create pre-commit hooks for these things. Conceivable, a pre-commit hook would filter out "garbage" files (unused private files). > As you can see, significant issues remain. This hardly surprises me. > The difficulty of synchronizing files reliably is *the* reason* Leo > has always used sentinels. I think @thin should still be used for situations where everybody uses leo most of the time. This is also a reason to proceed with @sentinelpadding - it's the simplest thing that could possibly work. -- Ville M. Vainio http://tinyurl.com/vainio --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "leo-editor" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/leo-editor?hl=en -~----------~----~----~----~------~----~------~--~---
