On 11/13/07, Anthony wikimail@inbox.org wrote:
That's complete nonsense, though. There are numerous ways to implement this without having any impact whatsoever on performance. Maybe the most straightforward solution would impact performance, but that doesn't mean "it simply cannot be implemented".
No, but what is true is that there is no way to have a magic word that consistently reflects the current user name, and can be used in various logical constructs, without invalidating the parser cache on each view (for re-views not by the same user). Invalidating the parser cache on each view for a moderately-trafficked page would be, presumably, a large hit to performance, thus the claim.
Allowing it to be used in logical constructs without a big performance hit would be difficult, as it'd require rewriting the parser cache (and preferably the parser itself), though still not impossible. In any case, if the intent is to allow logical constructs I can see why it'd be closed as wontfix. At least wontfix until code is provided or the foundation hires an actual staff.
Just inserting the username in *after* you've already parsed everything would be no big performance hit, necessarily, just as the username at the upper right isn't -- but as I say, it wouldn't do everything that the requesters really wanted.
The request in this thread, by Virgil Ierubino, didn't seem to require anything more than a last nanosecond substitution.
What if everything gets parsed and cached except the logical constructs? Or even better everything except the logical constructs which can't be immediately reconciled?
It also wouldn't be consistent with the behavior of other magic words, which is confusing.
A valid point, but simply renaming it <<CURRENTUSER>> or something could solve that.