Should the use of CacheItemPoolInterface be an implementation detail ?

[julienfastre]

The DocumentLockManager use CacheItemPoolInterface to store the lock.

This is comprehensive because lock must store some bytes, and be able to write and save it. It provides a quick way for locking file without requiring some adaptations in the database.

But what about those who do not use caching ? Should we not let dev use their own implementation ?

Proposal:

• DocumentLockManager becomes an interface in this bundle;
• the implementation which use CacheItemPoolInterface is moved to wopi lib bundle.

[github-actions[bot]]

Since this issue has not had any activity within the last 5 days, I have marked it as stale. I will close it if no further activity occurs within the next 5 days.