Does the ordering of nodes being returned from getNodesToLock affect
anything? Through some testing, deep trees under the sitetab really have
poor performance compared to wide trees. What I'm noticing is that
usecases such as ChangeNodeID go through its nodes in getNodesToLock in
a sorted order. I don't see anything there that would indicate that it
must be in sorted order. It looks like that was merely chosen for ease
of use into NodeSet.
Anyone have thoughts on this?
Richard
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]