On Sat, Mar 14, 2009 at 4:59 PM, Edward K. Ream <[email protected]> wrote:
> I'm not sure we want the "durability". I think of the situation as > follows. Positions only make sense in the context of a particular outline. > I mean the "snapshot" of the outline. Change the outline (snapshot) in any > way, and all bets are off. > > Archived positions make sense when writing the outline, and then reading the > *unchanged* outline. Any other use for archived positions seems dubious to > me. I don't think it's all that dubious to want to save the "path" to a node. Consider file system as an analogy: it certainly makes sense to store things like /foo/bar/baz.txt This path still points to the same file, even when we delete /foo/bar/blah.txt. Equally, we could have /12/45/111 and /1321/112/45/111 (Where those numbers are vnode id's). This way, we would almost never need to reconstruct the archived positions, provided that we didn't really make the node disappear. Ergo, no need to keep updating a database all the time. -- 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 -~----------~----~----~----~------~----~------~--~---
