Feature #3581

Site lock / code cache flushing mechanism

Added by Robert Lemke over 12 years ago. Updated about 11 years ago.

Status:
Resolved
Priority:
Must have
Assignee:
Category:
Cache
Start date:
2009-06-05
Due date:
% Done:

100%

Estimated time:
PHP Version:
Has patch:
Complexity:

Description

We need a concept and implementation for flushing critical caches like the code caches.

In order to flush the code caches, we need to completely lock the application so that no requests come through while the php classes are deleted or rebuilt (which obviously would lead to some fatal error). This locking mechanism should be as simple as the bootstrap checking for the presence of a file (like FLOW3_SITE_LOCK).


Related issues

Related to TYPO3.Flow - Task #3582: Concurrency stress testClosedRobert Lemke2009-06-05

Actions
Related to TYPO3.Flow - Feature #3649: Caches should be flushed on package version number changesResolvedRobert Lemke2009-06-12

Actions

Also available in: Atom PDF