HI, I'd like to do my stores into memcached as asynchronous stores as in the majority of cases I don't 'care' if they're stored successfully , as the next cache miss will attempt to store it again, obviously I realise that if I get an initial hit of a large number of concurrent access to the same cache-item then I will get multiple redundant hits, but I'm happy enough to live with that.
Am I better modifying the Enyim.Memcached client to support an Async Set [clearly a workqueue around the normal set command] (and provide you with another patch), or just wrap the existing client in my own facade to provide this functionality, i.e. what would 'a' (Enyim) prefer. Apologies if this isn't the *correct* forum for this discussion but I get no responses on the 'official' Enyim.memcached client website :( P.s. If this is a really bad idea please let me know why, but it seems that I should be ok with this in my case. -- - Ciaran
