CompileTimeCache
From APIDesign
(Difference between revisions)
(New page: Caches are usually created during installation time or during first execution/computation. Just like the CacheForModularity, they provide another store for information available elsewh...) |
|||
| Line 1: | Line 1: | ||
Caches are usually created during installation time or during first execution/computation. Just like the [[CacheForModularity]], they provide another store for information available elsewhere. This store is easily accessible, faster to read and use which then results in more optimal execution. | Caches are usually created during installation time or during first execution/computation. Just like the [[CacheForModularity]], they provide another store for information available elsewhere. This store is easily accessible, faster to read and use which then results in more optimal execution. | ||
| - | However caches can also be created during compilation. With [[JDK]]6 it is easier than ever | + | However caches can also be created during compilation. With [[JDK]]6 and the help of [[AnnotationProcessor]]s, it is easier than ever. This article shows what has to be done. |
Revision as of 11:24, 25 July 2009
Caches are usually created during installation time or during first execution/computation. Just like the CacheForModularity, they provide another store for information available elsewhere. This store is easily accessible, faster to read and use which then results in more optimal execution.
However caches can also be created during compilation. With JDK6 and the help of AnnotationProcessors, it is easier than ever. This article shows what has to be done.
Follow
