Change Details

The Virtual Rest Service for Parsoid content currently uses the Parsoid v1 API. Once RESTBase is deployed and well tested we should start switching this over to RESTBase, so that VisualEditor, Flow and other consumers can profit from the smaller HTML without inline data-parsoid & faster load times. For a smooth migration we should support both backends & have the option to switch between them using a config flag in MediaWiki. Both infrastructures (RESTBase and Parsoid Varnishes) will be available in parallel during the transition period.

The Virtual Rest Service for Parsoid content currently uses the Parsoid v1 API. Once RESTBase is deployed and well tested we should start switching this over to RESTBase, so that VisualEditor, Flow and other consumers can profit from the smaller HTML without inline data-parsoid & faster load times. For a smooth migration we should support both backends & have the option to switch between them using a config flag in MediaWiki. Both infrastructures (RESTBase and Parsoid Varnishes) will be available in parallel during the transition period. This is also a good opportunity to clean up some things in this area: - remove the `/parsoid/` prefix (requires some changes in the VRS base class) - adjust URL schema to current restbase layout (`/page/html/{title}/{revision}`). - share / generalize the config & setup for VRS & Parsoid / RESTBase: factory function / singleton?

The Virtual Rest Service for Parsoid content currently uses the Parsoid v1 API. Once RESTBase is deployed and well tested we should start switching this over to RESTBase, so that VisualEditor, Flow and other consumers can profit from the smaller HTML without inline data-parsoid & faster load times. For a smooth migration we should support both backends & have the option to switch between them using a config flag in MediaWiki. Both infrastructures (RESTBase and Parsoid Varnishes) will be available in parallel during the transition period. This is also a good opportunity to clean up some things in this area: - remove the `/parsoid/` prefix (requires some changes in the VRS base class) - adjust URL schema to current restbase layout (`/page/html/{title}/{revision}`). - share / generalize the config & setup for VRS & Parsoid / RESTBase: factory function / singleton?