On Fri, Aug 28, 2009 at 5:00 AM, Edward K. Ream<[email protected]> wrote:
> My present opinion is that caching should be disabled for all nodes except > @thin nodes. The read logic for the various kinds of @<file> nodes is And @auto, @auto-rst. What other types of @<file> nodes do we have that are round-tripped? > subtly different, and I am far from convinced that caching has been > thoroughly tested. > Presumably uA's survive in @thin trees because of the the so-called "hidden > machinery" in @thin files, that is, the descendentTnodeUnknownAttribute in > the <v> element in the @thin node. The hidden machinery exists only for > @thin trees. Yes, because only @thin files have uAs (because they have persistent gnx's). > in the "helpful" conversion code. So I think we should just advise people > not to use them in cooperative environments and leave it at that. Yes, that's the best plan for now. g.es a brief warning about them though. > The problems happen in the trunk, so I don't see how we can pretend there > are no problems. It may be that the problems are confined to @file nodes, > and that we can solve those problems simply by never caching @file nodes, > but I'm having troubles with the trunk, and I know of no changes that would > have broken the trunk. In other words, I think the problems existed in Leo > 4.6.2. Yeah, I do believe the problem is confined to the @file nodes. When you disable the caching for @file nodes (I still think it's better to leave it on for other file types), please do it in 46-maint branch first so that we can have it in 4.6.3. -- 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 -~----------~----~----~----~------~----~------~--~---
