Feature #36568
Make use of multiple file monitor instances easier/possible
Status: | Resolved | Start date: | 2012-04-25 | |
---|---|---|---|---|
Priority: | Should have | Due date: | ||
Assigned To: | Robert Lemke | % Done: | 100% |
|
Category: | Monitor | |||
Target version: | TYPO3 Flow Base Distribution - 1.1 | |||
PHP Version: | Complexity: | |||
Has patch: | No |
Description
The fact that the FileMonitor doesn't use it's identifier internally (for caching) and the fact that the ModificationTimeStrategy is singleton do not really make the use of multiple file monitor instances easier…
Associated revisions
[!!!][FEATURE] FileMonitor now uses identifier and has getIdentifier()
This change makes the FileMonitor use the identifier internally and
provides a getIdentifier() method. With this, using multiple file
monitors becomes feasible.
The "ChangeDetectionStrategyInterface" contains the two new methods
"setFileMonitor" and "shutdownObject" now, so if you implemented your
own change detection strategy, you need to implement those.
The ModificationTimeStrategy provided with FLOW3 is no longer singleton
and thus usable with multiple file monitor instances in parallel.
Change-Id: Ic90168e0fa1a156a343be0997631b4995ec1ae0c
Resolves: #36568
Releases: 1.1
History
#1 Updated by Gerrit Code Review over 3 years ago
- Status changed from Accepted to Under Review
Patch set 1 for branch master has been pushed to the review server.
It is available at http://review.typo3.org/10764
#2 Updated by Gerrit Code Review over 3 years ago
Patch set 2 for branch master has been pushed to the review server.
It is available at http://review.typo3.org/10764
#3 Updated by Gerrit Code Review over 3 years ago
Patch set 3 for branch master has been pushed to the review server.
It is available at http://review.typo3.org/10764
#4 Updated by Karsten Dambekalns over 3 years ago
- Status changed from Under Review to Resolved
- % Done changed from 0 to 100
Applied in changeset cf6bb6911b4f609a59a8cf7986f364162a18abed.