The discussions around use of the dynamic metadata resolver suggest that people would really like to see support for on-disk caching across restarts.
The most logical way to handle this seems to storing things based on a hash of the entityID.
This code can already load from file:/// URLs, so transforming the request into that form using the hash might be a simple way to handle it, and it's just a matter of doing the backup step.
Considering adding support for verifyBackup="false". Its trivial to add the code for, but it involves adding a {{BatchLoadMetadataFilterContext}} parameter to the dofilters method which makes me slightly nervous. I suppose you could claim that reloading metadata from the backing store on restart is a "Batch Load" operation....
Fixed
Pinned fields
Click on the next to a field label to start pinning.
The discussions around use of the dynamic metadata resolver suggest that people would really like to see support for on-disk caching across restarts.
The most logical way to handle this seems to storing things based on a hash of the entityID.
This code can already load from file:/// URLs, so transforming the request into that form using the hash might be a simple way to handle it, and it's just a matter of doing the backup step.