Change Details

Because Hovercards essentially display the content of the summary end point, it was identified as a good candidate for this evaluation. The goals of this evaluation are: 1. Determine if RESTBase scaling is sufficient for web traffic 2. Compare statistics such as latency and response time vs using the MediaWiki API 3. Determine if using RESTBase for APIs is a valid strategy for Desktop/Mobile web To support this evaluation, it should be possible to configure Hovercards to use a REST endpoint as the source. Add a config variable that when true uses the REST api endpoint, when false uses the mediawiki api (as it does currently). The rest api endpoint does not need to fallback to the mediawiki api when REST is not responding. Relevant links: https://www.mediawiki.org/wiki/RESTBase https://en.wikipedia.org/api/rest_v1/#!/Page_content/get_page_summary_title

Because Hovercards essentially display the content of the summary end point, it was identified as a good candidate for this evaluation. The goals of this evaluation are: 1. Determine if RESTBase scaling is sufficient for web traffic 2. Compare statistics such as latency and response time vs using the MediaWiki API 3. Determine if using RESTBase for APIs is a valid strategy for Desktop/Mobile web To support this evaluation, it should be possible to configure Hovercards to use a REST endpoint as the source. Add a config variable that when true uses the REST api endpoint, when false uses the mediawiki api (as it does currently). The rest api endpoint does not need to fallback to the mediawiki api when REST is not responding. The scope of this task does not include enabling this config variable to true and it should default to use non-REST endpoints. Relevant links: https://www.mediawiki.org/wiki/RESTBase https://en.wikipedia.org/api/rest_v1/#!/Page_content/get_page_summary_title

Because Hovercards essentially display the content of the summary end point, it was identified as a good candidate for this evaluation. The goals of this evaluation are: 1. Determine if RESTBase scaling is sufficient for web traffic 2. Compare statistics such as latency and response time vs using the MediaWiki API 3. Determine if using RESTBase for APIs is a valid strategy for Desktop/Mobile web To support this evaluation, it should be possible to configure Hovercards to use a REST endpoint as the source. Add a config variable that when true uses the REST api endpoint, when false uses the mediawiki api (as it does currently). The rest api endpoint does not need to fallback to the mediawiki api when REST is not responding. The scope of this task does not include enabling this config variable to true and it should default to use non-REST endpoints. Relevant links: https://www.mediawiki.org/wiki/RESTBase https://en.wikipedia.org/api/rest_v1/#!/Page_content/get_page_summary_title