Closed Bug 1657082 Opened 2 years ago Closed 1 year ago

[machinery][3rd party] Refactor machinery to be purely server-side


(Webtools Graveyard :: Pontoon, enhancement, P4)



(Not tracked)



(Reporter: Pike, Unassigned)


Right now, each variant of machinery needs to be known in both the front-end and the back-end. Let's refactor this so that it's purely on the server side.

This is good for Mozilla's instance, but also for 3rd party installs that might want to trigger other combinations.

There's two basic approaches:

  • Have one API publicizing all machineries for a locale, and then have the front-end ask each machinery.
  • Have one API for all machineries, and dispatch the request server side, with each response being marshalled into one global response.

The first approach would be relatively straight-forward, but still keeps a lot of individual requests between the frontend and the backend.

The latter approach requires parallel IO from the server to external machineries, and it should respond incrementally to not regress responsiveness of the current UX. We can use asyncio now, and we can talk to a Django StreamingHttpResponse. That requires a sync generator, though, We should be able to fake that via The front end would read the response incrementally from fetch via

This would require an update to Django 3.0, but no further at this point.

Matjaz and I talked about this a bit last week, and it's probably good to do this in two steps, first with just unifying the handling and exposing the metadata for the locale, but keeping an xhr for each engine.

And then folding the requests into one streaming one later. Let's keep this bug for the first step.

Adding myself as a mentor, happy to help with advice if someone wants to pick this up. Putting in P4 as we don't see this on a timeline ourselves.

Mentor: l10n
Priority: -- → P4
Mentor: l10n
*This bug has been moved to GitHub.*

*Please check it out on*
Closed: 1 year ago
Resolution: --- → MOVED
Product: Webtools → Webtools Graveyard
You need to log in before you can comment on or make changes to this bug.