[AgileWiki] reasonable speed and reasonable simplicity, a "good enough" solution

[Bill la F. <bil...@su...>]

The namespace must be cached, otherwise it is just too slow, especially 
when displaying a document with lots of references.

The problem is, can we update the cache or even invalidate it when 
appropriate? With each new type of CSec we add, we add significantly to 
the complexity of any such logic.

But there is one "cheat" which is likely "good enough". Simply 
invalidate all namespace caches whenever a transaction completes. For 
queries then the namespaces are always valid, and for updates the 
namespaces are valid at the beginning of the transaction.

This then opens the door wide for easily implementing all kinds of 
CSecs, including infoset intersection, infoset subtraction, and 
filtering on various criteria. Effectively then we can have as much 
power to define infosets as you have with SQL.

Should prove interesting. :-)

Bill