Page MenuHomePhabricator

Ability to disable user-specific SSR
Open, Needs TriagePublic5 Story Points

Description

In order to allow for smooth deployment and easier debugging it would be beneficial to be able to control in which scenarios requests against the newly introduced SSR service are performed. This is particularly important as results of the requests for user-specific termbox markup are not cached/hardly cachable.

AC:

  • there exists a config variable "termboxUserSpecificSsrEnabled" to Enable/Disable server-side rendering (SSR) for user-specific termbox markup. The default setting is <code>true</code>. It only comes into effect if the general "termboxEnabled" is <code>true</code>. If disabled, user-specific termbox markup will only be created by client-side rendering after initial diplaying of the generic termbox markup. See termboxEnabled

Event Timeline

Restricted Application added a subscriber: Aklapper. · View Herald TranscriptMar 12 2019, 10:47 AM
Lea_WMDE set the point value for this task to 5.Mar 13 2019, 4:08 PM

Users with specialized data are not cached. If we need to reduce the number of requests, not ever sending SSR requests in those cases (i.e. showing nothing), but forcing users to wait for the client side action to kick in would be an option.
If we don't have this, and run into problems with the number of requests, the only way to reduce the number of requests would be disabling the new termbox functionality completely, falling back to the current state.

Addshore moved this task from incoming to in progress on the Wikidata board.Mon, Mar 25, 4:04 PM