No it is not. you are confusing the Doctrine Cache lifetime, and the timestamp for ``isFresh``

- Doctrine Cache has an expiration model: you set the lifetime when caching.
- The Gherkin Cache interface is based on a validation model: the cache can be valid forever (it does not expire), but before using, Gherkin will call ``isFresh`` with the time of the latest modification of the ``.feature`` file. This way, it can know whether the cache was created after the latest change (and so can be used) or before the latest change (and so is outdated and the source needs to be parsed again)

If you want to make a comparison with the HTTP cache, it is the same than setting the ``Expires`` header (Doctrine Cache lifetime) vs setting the ``Last-Modified-At`` header (Gherkin needs)

with your implementation, a modification of the ``.feature`` file will never be taken into account, until you clear your Memcached.