Feature #2305
Automatic flushing of AOP Proxy Cache
| Status: | Resolved | Start date: | 2008-12-12 | |
|---|---|---|---|---|
| Priority: | Should have | Due date: | ||
| Assigned To: | Robert Lemke | % Done: | 100% |
|
| Category: | AOP | |||
| Target version: | TYPO3 Flow Base Distribution - 1.0 alpha 1 | |||
| PHP Version: | Complexity: | |||
| Has patch: |
Description
Similar to the automatic flushing of the Reflection Cache (or parts of it) the AOP proxy classes should be rebuilt whenever a class is modified - at least in the development context. However, that's only realistic if rebuilding the cache doesn't take too long so it remains to be seen if this is realistic or not.
Related issues
Associated revisions
- FLOW3: (AOP) Implemented a completely new initialization method for the AOP framework which now supports some intelligent caching mechanism: If class code changes somewhere, the affected proxy classes are rebuilt automatically, still valid proxy classes are untouched. If aspects change (or are added / removed) all proxy classes are rebuilt. All based on the new File Monitor feature. Resolves #2305
- FLOW3: Fixed configuration to assure that the file monitoring is really disabled in Production context.
History
#1 Updated by Robert Lemke over 6 years ago
- Status changed from New to Resolved
- % Done changed from 0 to 100
Applied in changeset r1756.