questions about caching in a webservice
-
Hello, 1. I was under the impression that cache.insert was thread safe. Is this true? 2. Also you cannot count on a cached item staying in the cache until it expires because it maybe be removed for memory reasons - true? 3. Are there rules of thumb for how much data is too much to cache? which would then just cause the cache to be continually shuffled with objects. I know it would be depend on many things...but if there any basic parameters? Also there are different patterns of how to implement caching one of which is called: Asynchronous pull loading - which is what I probably should use. It requires implementing a dispatcher to consolidate data, a cache and the business logic. I don't have lots of data consolidation to do but do have a situation where I want to pull data all at once into the cache, then expire on a regular and fairly infrequent basis. 4. Does this sound like the kind of pattern for me to use then? 5. Would the dispatcher then just be a method called asynchronously to pull data on the cache object expiration and then also as a callback if the cache object is removed for other reasons? Thanks for enlightening me on any of this.
-
Hello, 1. I was under the impression that cache.insert was thread safe. Is this true? 2. Also you cannot count on a cached item staying in the cache until it expires because it maybe be removed for memory reasons - true? 3. Are there rules of thumb for how much data is too much to cache? which would then just cause the cache to be continually shuffled with objects. I know it would be depend on many things...but if there any basic parameters? Also there are different patterns of how to implement caching one of which is called: Asynchronous pull loading - which is what I probably should use. It requires implementing a dispatcher to consolidate data, a cache and the business logic. I don't have lots of data consolidation to do but do have a situation where I want to pull data all at once into the cache, then expire on a regular and fairly infrequent basis. 4. Does this sound like the kind of pattern for me to use then? 5. Would the dispatcher then just be a method called asynchronously to pull data on the cache object expiration and then also as a callback if the cache object is removed for other reasons? Thanks for enlightening me on any of this.
I don't know, as I have not done much webservice caching. Is there anything that can answer your question in this article (XML Web Service Caching Strategies[^])
Yusuf Oh didn't you notice, analogous to square roots, they recently introduced rectangular, circular, and diamond roots to determine the size of the corresponding shapes when given the area. Luc Pattyn[^]
-
I don't know, as I have not done much webservice caching. Is there anything that can answer your question in this article (XML Web Service Caching Strategies[^])
Yusuf Oh didn't you notice, analogous to square roots, they recently introduced rectangular, circular, and diamond roots to determine the size of the corresponding shapes when given the area. Luc Pattyn[^]