There is no good reason why every web has to have the same store implementation.
Make the store implementation pluggable on a per web basis.
The current store selection has to be the default. Then, a $cfg item should allow the selection of different stores on a per-web basis (note that this can't be done in Preferences because it isn't dynamic. Once you pick a store implementation for a web, there is (currently) no simple way to switch it to a different implementation dynamically.
was also part of this, should this be merged in? Setting waiting for feedback).
I'm not happy with this "fix" going into TWiki4. TWiki4's current behaviour is not a bug, this is an extension. I stumbled over exactly that change in
when testing TWiki's performance with Dprof:
can be called really often during a single view, and in a topic like TWikiVariables
it made the previously innocent sub pop up in the top 15 CPU eaters.
Absolutely not; this must not be merged
. If it was synched it must be reverted!
This is the thin end of a new experimental wedge in DEVELOP. it's not even intended for a minor