Actually, I just realized it might better be fixed in NHibernate.Caches.MemCache.MemCacheClient provider rather than in the Memcached.ClientLibrary.MemcachedClient library.
I thought NH wrapper calls the default method Delete(string key) which sends DateTime.MaxValue but it turns out DateTime.MaxValue is actually treated by the actual Delete method as a signal not to send any expiration date to memcached server. Which made me think the NH wrapper can't possibly be invoking Delete(string key). Indeed, looking at NHibernate.Caches.MemCache.MemCacheClient's method Remove(object key) I see the following line: this.client.Delete(this.KeyAsString(key), DateTime.Now.AddSeconds((double) this.expiry)); So rather than keeping NH wrapper supply an expiration date and making Memcached.ClientLibrary.MemcachedClient ignore, which is kinda silly, I think we should modify NHibernate.Caches.MemCache.MemCacheClient to not supply expiration date instead. Right? -- You received this message because you are subscribed to the Google Groups "NHibernate Contrib - Development Group" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/nhcdevs?hl=en.
