Re: Efficient read-only cloning?

> I don't think you can, really.

I agree. Hence my suggestion of clone-while-making-read-only, to avoid an
extra tree-walk.

Note that for XML design tools, which may edit the DTD, cloning the kids
isn't enough. To support those, EntityReference also has to be aware when
Entity has changed and refresh itself. Which brings up all the usual nasty
questions about exactly when Entity (and hence the application) actually
discovers this change, plus another set of challenges to deal with if/when
we add multitasking support.

______________________________________
Joe Kesselman  / IBM Research
Unless stated otherwise, all opinions are solely those of the author.

Received on Wednesday, 23 September 1998 13:16:59 UTC