Now that the "short sentinel" idea is sort of dead, perhaps it could be resurrected by "sentinel compression"? New sentinels would *always* be of the current kind, but old sentinels would be short (single running base64 index, without table).
Compressing a @thin file would never be automatic - rather, it's a ceremony to be performed when all the branches to be merged to it have been merged in (e.g. after a release), usually by a single person (e.g. in Leo, Edward would be the only one with the authority to compress sentinels... apart from plugins that have a different maintainer). This may also be beneficial because it provides a visual clue about "new" nodes. -- 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.
