Closed (fixed)
Project:
Translation Management Tool
Version:
8.x-1.x-dev
Component:
Core
Priority:
Normal
Category:
Feature request
Assigned:
Reporter:
Created:
25 Apr 2016 at 13:23 UTC
Updated:
11 May 2016 at 15:54 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #2
edurenye commentedAdded cache for remote languages.
Comment #3
miro_dietikerAnd how long is the cache persisted?
What if the provider adds a language and it doesn't show up to the end user?
Do we need to offer a Clear / update button to the user in the translator?
Comment #4
berdirWe already have identical caching for two language calls. You have to resave the translator or do any other form of cache clearing already in such a case.
Comment #5
miro_dietikerYeah i see that in the diff. :-)
I think we should do a followup about the UX aspect of that.
Comment #6
berdirAs discussed, the current pattern of writing all caches on every change is a lot of overhead.
We should only do the specific cache set in each method, atleast here for the new one, OK if we don't update the existing ones.
Comment #7
edurenye commentedDone, changed just the new one.
Comment #8
berdiralmost ;)
what we are missing now is the check if languages should be cached, we have to check that here as well.
not even sure that works properly, because I don't think you can have an annotation property with spaces..?
Comment #9
edurenye commentedDone those changes.
Comment #10
edurenye commentedFixed incoherence.
Comment #12
berdirThanks, committed.