Change Details

In order to avoid blocking mediawiki rendering the termbox SSR request should be configured with a timeout. The fallback behavior already in place should come into effect in case the timeout is reached. In case the fallback behavior is used, the result should not be persisted in ParserCache.

**Motivation** In order to avoid blocking mediawiki rendering the termbox SSR request should be configured with a timeout. **Timeout limit** Possibility to find that out: Render a couple of items, and see what would be an unusual time of rendering If the number is too high, we would impact the whole service of Wikidata and mediawiki (like 60 seconds) Risk of being too low: We would only rely on client side editing, which would create more load on low performance clients **User perspective** - They would not see anything until the timeout was reached, and then client side rendering would kick in, and then the user would see stuff (considering their browser supporting java script) **Acceptance Criteria** [] There is a timeout limit in place when the SSR request is stopped. [] If the SSR request is stopped, client side rendering happens as a fallback [] If the SSR request is stopped due to a timeout, ParserCache should not persist any results [] The timeout limit is neither badly affecting Wikidata/Mediawiki performance nor always resulting in client side fallback activity. **Note** If along the way you find out, what happens on the SSR side (is it still trying to render sth or will it realize that the client has hung up), please make note and let everyone know.

**Motivation** In order to avoid blocking mediawiki rendering the termbox SSR request should be configured with a timeout. **Timeout limit** Possibility to find that out: Render a couple of items, and see what would be an unusual time of rendering If the number is too high, we would impact the whole service of Wikidata and mediawiki (like 60 seconds) Risk of being too low: We would only rely on client side editing, which would create more load on low performance clients **User perspective** - They would not see anything until the timeout was reached, and then client side rendering would kick in, and then the user would see stuff (considering their browser supporting java script) **Acceptance Criteria** [] There is a timeout limit in place when the SSR request is stopped. [] If the SSR request is stopped, client side rendering happens as a fallback [] If the SSR request is stopped due to a timeout, ParserCache should not persist any results The fallback behavior already in place should come into effect in case the timeout is reached.[] The timeout limit is neither badly affecting Wikidata/Mediawiki performance nor always resulting in client side fallback activity. **Note** In case the fallback behavior is usedf along the way you find out, what happens on the SSR side (is it still trying to render sth or will it realize that the client has hung up), the result shouldplease make not be persisted in ParserCachee and let everyone know.