| Summary: | Possibility to reload code type cache for all locals | ||
|---|---|---|---|
| Product: | z_Archived | Reporter: | Christoph Thommen <christoph.thommen> |
| Component: | Scout | Assignee: | Project Inbox <scout.core-inbox> |
| Status: | CLOSED FIXED | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | P3 | CC: | ivan.motsch |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows 7 | ||
| Whiteboard: | |||
|
Description
Christoph Thommen
Correction: It does actually reload the cache, but clears the other languages out. If more than one language is refreshed, only the last-refreshed language is loaded again, all the others are cleared again. This is right, it first clears the cache for each language and then reloads the calling language. The latter part could be omitted without any change in functionality but is there for performance optimization. Since the caller most likely uses the code type it is getting a code change client notification anyway and is then getting the code type which triggers the cache refresh. In Short: When reloading a code type it is sufficient to clear the cache, since the getting of a code type re-publishes the cache. If your use case is to load physically reload all languages you might create a scout server job that loops over all used locales and gets the code type. That way all languages are re-populated immediately. For example every night if some code relevant data is changed. Solution is ok for our use case |