On Thu, Mar 26, 2009 at 1:20 AM, Ville M. Vainio <[email protected]> wrote:
> > On Thu, Mar 26, 2009 at 3:45 AM, Edward K. Ream <[email protected]> > wrote: > > >> Hashing to rescue! For file foo.py ver 3, we have a private version > >> 2368237aaee.txt.py. The name is the hash digest of contents of foo.py. > > Grab a chair. > > *this is the speedup cache I've been talking about* Very cool. I don't understand the details, but clearly it opens many possibilities. > > > It will not contain @thin like nodes. It will contain the whole data > structure in a pickle [(gnx1, h1, b1, (gnx1.1, h1.1, b1.1)), > (gnx2...)] > > This will allow us to avoid the slow sentinel scanning. What you are saying, as I understand it, is that the hidden (shadow) files could have any format we want. They don't have to contain "traditional" sentinels. They wouldn't even actually have to be text files! BTW, this has a bearing on the (misnamed) question of "what do we call @file! ?". The proper question is, instead, "will there still be a role for @thin?". My first thought was, "surely yes": @thin is the most elegant and safest way when collaboration is not a factor. All data is in a single file, so syncing issues never arise. But now I am not so sure. If caching speeds up sentinel scanning, a strong case can be made for using @shadow for *all* files, even in situations where collaboration is not a factor at all. Again, this is very cool. Using @file! for *all* situations looks like a big performance win. > > . Just wanted to throw this out quickly. I'm glad you did. I want to clarifysome other questions on this thread before delving into your idea further, but this is a great idea that I want to pursue immediately. 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 -~----------~----~----~----~------~----~------~--~---
