Expiration time for workers

[aleksei4er]

If cache ttl times out while php worker executing, it would be great to update feature flag value.

[mKnoop]

Nice Idea. But i think we should also consider the cache hash keys for the expiration time and not set the value for all entries once

[b3nl]

Nice Idea. But i think we should also consider the cache hash keys for the expiration time and not set the value for all entries once

@mKnoop What is your reasoning behind this?

[mKnoop]

Nice Idea. But i think we should also consider the cache hash keys for the expiration time and not set the value for all entries once

@mKnoop What is your reasoning behind this?

The implementation in this pr will set a global expiration time if a new cache entry will be written. If later in the process we want to refetch a existing item from the cache the expiration time from the last new entry will be used instead of the expiration time of the specific entry. So in my opinion the expiration time should be item specific and the optimal workflow should be:

Existing entry:

1. Try to fetch from the memory cache
2. If item has been found check if the time for this specific entry has been expired
3. If item is not expired, return the item

new entry:

1. Try to fetch from the memory cache
2. If no item has been found try to fetch from cache pool and return found item
3. If the item can also not be found in the pool fetch entry from the activator and write entry to the memory cache and cache pool
4. Set the expiration time for this specific item

I think this should cover the initial proposal that in long running processes the memory cache value will also be refreshed after the expiration time