On 11/19/2015 04:39 PM, [email protected] wrote:
1) No l10n on back-end. All l10n on front-end[0]. [0] Exceptions may exist, they are rare. You case is probably not one of them. When in doubt, ni? me or stas :)
What's the plan for this and service-workers? Specifically, background-y APIs are all moving to targeting service workers, replacing our system message mechanism that wakes up content pages directly. Specifically, it seems like the push API (https://w3c.github.io/push-api/), background sync API (https://wicg.github.io/BackgroundSync/spec/), and others are intended to be processed in service workers and notifications generated (https://notifications.spec.whatwg.org/) without necessarily waking up/creating a front-end/content page.
It's not a problem right now for most of the special cases because we always have to have a content-page around, but it seems like it will be an architectural problem if we need to spin-up content pages once service workers are more fleshed out and we start to move over to standardized APIs.
Andrew _______________________________________________ dev-fxos mailing list [email protected] https://lists.mozilla.org/listinfo/dev-fxos
