Last modified: 2013-03-15 11:07:23 UTC
CentralAuth is causing needless page/user invalidations. Existing bad code paths: - Title cache invalidation should be done only when email settings actually changed LoginForm::execute LoginForm::processLogin LoginForm::authenticateUserData CentralAuthPlugin::updateUser User::saveSettings Title::invalidateCache - we should invalidate user cache only when there are changes that would need different rendering logic, not for every centralauthhooks session reload User::getOption User::loadOptions User::load User::loadFromSession wfRunHooks call_user_func_array CentralAuthHooks::onUserLoadFromSession CentralAuthHooks::initSession User::invalidateCache
http://svn.wikimedia.org/doc/classUser_a124949b4a526ad6885f7f98816d3862d_icgraph.png
lowering priority, unassigning reedy.
Think this is mostly done... shouldn't block 1.18
(In reply to comment #1) > http://svn.wikimedia.org/doc/ > classUser_a124949b4a526ad6885f7f98816d3862d_icgraph.png 404 now. :-/ Wondering what's the status of this.