Hi all, I&#39;m working away on the kmusicbrainz library and one of the things I want to do is create a query cache so that common lookups don&#39;t need to always wait on the network or can be retrieved from cache when the client is not connected to the net. <br>
<br>The queries themselves are typically either a UUID type string, an artist or album name or a disc Id string. The results are chunks of XML. Is there a standard key / value style string caching mechanism in any of the libs or that could be borrowed from an application?<br>
<br>If not, what approach would anyone suggest to an issue like this? I&#39;d like to have a few features supported:<br>1. query aging: after a (configurable) period of time, a known query should go stale so it can be re queried and the data refreshed<br>
2. Performant for string keys: sadly most of the keys will be strings (sometimes pretty aribitary ones) so fast string key lookup would be a good thing (tm)<br><br>If I end up writing this from scratch, would a file approach be best or should I look at using sqllite or similar?<br>
<br>cheers<br>Nathan<br>