On Thu, 17 Jul 2003 11:53:56 +0200 (Romance Daylight Time) Vadim Zeitlin <[EMAIL PROTECTED]> wrote:
> It's not a solution because we're back at case #1: what happens now > when a > folder is renamed? The tree needs to be notified and rebuild all its > internal data structures... Well, ok, it's doable, but not ideal. This isn't the same case as renaming references. This visible name tree isn't stored permanently. It's just a cache for some operation over identifier-based tree. This cache must have autoreset -- whenever some visible name changes or folder is added, it rebuilds corresponding part of visible name tree. We need decentralized configuration change notification (e.g. listeners) anyway. > [A] > [A/B] > ... all data for the folder B ... > VisibleParent=C # folder tree checks this > > [C] > [C/B] > LinkTo=A/B # or "AliasFor" This looks like my MovedTo/MovedFrom pairing. I dropped this idea, because it introduces redundancy into configuration. Redundancy is easy to get wrong and it makes it hard to edit by hand. ------------------------------------------------------- This SF.net email is sponsored by: VM Ware With VMware you can run multiple operating systems on a single machine. WITHOUT REBOOTING! Mix Linux / Windows / Novell virtual machines at the same time. Free trial click here: http://www.vmware.com/wl/offer/345/0 _______________________________________________ Mahogany-Developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/mahogany-developers
