Project:
| View Revisions: Issue #32041 | [ Back to Issue ] | ||
| Summary | 0032041: API change required for cached preference mechanism | ||
| Revision | 2016-01-28 16:02 by caristu | ||
| Description | As explained in issue[1] a new mechanism to store preference values in cache is going to be implemented in a generic way. Currently this approach is used to store the value of a preference in particular () using the UnpagedRequestCachedPreference.java class. This class is going to be replaced with a new class CachedPreference which implements the logic to keep the value for multiple preferences, including the one being stored with UnpagedRequestCachedPreference. This API change consists of removing UnpagedRequestCachedPreference class and create the new CachedPreference class. [1] https://issues.openbravo.com/view.php?id=32039 [^] |
||
| Revision | 2016-01-28 13:59 by caristu | ||
| Description | As explained in issue[1] a new mechanism to store preference values in cache is going to be implemented in a generic way. Currently this approach is used to store the value of a preference in particular () using the UnpagedRequestCachedPreference.java class. This class is going to be replaced with a new class CachedPreference which implements the logic to keep the value for multiple preferences, including the one being stored with UnpagedRequestCachedPreference. This API change consists of removing UnpagedRequestCachedPreference class and create the new CachedPreference class. |
||
| Copyright © 2000 - 2009 MantisBT Group |
 |