On Mon, Dec 19, 2011 at 11:59 AM, Edward K. Ream <[email protected]> wrote: > If all (or almost all) data appears in a Leonine sqlite db we can say > the following: > > - There is no need for a Leo cache. > - There is no need for private @shadow files. > - We can use the @shadow algorithm for *all* files, including @file, > @auto, etc.
Wrong, wrong, wrong. @shadow will *never* be the model for most files because it demotes structure info to second-class status, namely, personal preference grafted on to the "real" data. But the *essence* of Leo is that structure is first-class data. @shadow is fine for non-cooperative (private) environments. In that case, the "preference" structure is, in fact, the only structure there is. But in shared environments outline structure must be part of each external file. Thus, sentinels are, in general, essential as well. This must be the fourth or fifth time I have rediscovered this basic principle. In the past, the emphasis has been mostly on sentinels, but here we see that the underlying principle is that outline structure must be first-class data in shared (cooperative, distributed) environments. So this is progress of a sort. As a direct consequence, any approach that abandons sentinels must be rejected. I don't know, in detail, this affects the current discussion, but I think Seth and Hans have ideas that are compatible with this principle. Edward -- 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.
