This thread looks to be a little on the old side and therefore may no longer be relevant. Please see if there is a newer thread on the subject and ensure you're using the most recent build of any software if your question regards a particular product.
This thread has been locked and is no longer accepting new posts, if you have a question regarding this topic please email us at support@mindscape.co.nz
|
I'm looking at the ICache interface with an eye toward writing an Azure cache provider. I need to solve a problem with a small but very hot table across a large web farm. The "AddItem" method states "Adds an item into the cache, only if it does not already exist." If I ignore this advice and always write, does that turn my cache into a write-thru cache? One that, assuming all access is through Lightspeed and I maintain proper locking semantics with the cache, remains up to date? Edit: I found this thread which clarifies that the L2 cache is write-thru and, with a proper distributed caching provider, works as desired: http://www.mindscapehq.com/forums/thread/3455 Can you clarify the AddItem semantics? I ask because implementing it adds an additional lock to the implementation that affects performance. |
|
|
I can confirm that your AddItem implementation is not required to check whether the item is already in the cache. Neither of the built-in cache providers perform such a check. I tried to figure out what the documentation was trying to suggest, but I think the documentation is just wrong. Thanks for alerting us and we'll get the documentation updated. |
|