Optimisation: Cache language files for Vorto properties

[PeteDuncanson]

Optimisation: Cache language files for Vorto properties

[mattbrailsford]

Good spot. Maybe just loading it once per "editor load" would be ok. So when you open an editor it just gets requested once and all vorto probs on the front end use the same result.

I'll have a play when I have a sec though.

Thanks for reporting.

[PeteDuncanson]

@simonech I logged that other issue with service workers we discussed here too btw: http://issues.umbraco.org/issue/U4-11388

[simonech]

Could also be done using the "sync" mechanism the same way you sync open tabs and current tab.
You just load the languages once and sync its content to all other properties in the page.

Anyway this seems like a more generic issue. There should be a way to adopt the "service worker" approach (or something similar) to all API calls done in the backend, and just load them once per editor (even if reused in different properties). For example the configuration of doctypegrid editor, where every "cell" loads the overall configuration. But this is beyond the scope of this issue :)