Port XML-RPC API server or convert it

Created on 29 May 2023, about 1 year ago
Updated 3 July 2023, 12 months ago

Problem/Motivation

The XML-RPC API supports the use of remote glossaries as a source for various data: alphabar, latest, random entry, stats, top entries, and WOTD.

It is not yet ported to the 8.x branch, so it needs to be. However, XML-RPC has a number of issues

  • It does not expose cacheability data, although all the data this API provides is read-only and most is highly cacheable
  • XML has fallen out of fashion for over 10 years now, and most remaining XML RPCs are SOAP-based anyway
  • OTOH, just porting to 8.x without converting may be cheaper

Steps to reproduce

n.a.

Proposed resolution

When handling this issue, decide on the format to use: XML-RPC or something else, likely a plain JSON endpoint.

Remaining tasks

Decide on the API format and implement the port.

User interface changes

None.

API changes

Either none (XML-RPC) or conversion to a new API format.

Data model changes

None.

πŸ“Œ Task
Status

Fixed

Version

1.0

Component

Code

Created by

πŸ‡«πŸ‡·France fgm Paris, France

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

Production build 0.69.0 2024