issue-71: code changes after reviews

synced to ehcache/master and ready to be merged
Is this for putIfAbsent()? Why even have this outcome anyway - the mutation never happened, after all? It's also not wired in anywhere. 

Similar comment for UPDATED - will it even be possible to use this, given that the write through pattern assumes an "upsert" semantics on the writer at the moment?