Without constructive criticism, no one can hope to improve, and that's why I am thankful for everything you say. Other comments I received were to the tune of "you walked around the room too much" or "why didn't you walk around more". I appreciate everything you have to say, and hope that you will continue to "dish it out" =)
That said, I did make my point early on - where to put the caching code, and why. Anybody can read the docs and find out which config file to change and how in order to turn of encryption. Most people won't know if "server" or "client" code should be responsible for the data in the cache. More so, even fewer will know who should control what get's cached, and how to do that.
Also, as you recall, the use of the CAB - when it was introduced - was exactly the same as the original caching code. Everything else was controlled by config files. That was the underlying theme - when you work correctly, it becomes trivial to swap out implementations. This is due to the rich abilities of the CAB to control it's behaviour at runtime via config files.
All in all, I think it went rather well - don't you ?
Udi. Yes it went really well. I just wish there had been more of a real world demo of the use. For example, how to share a chache between two applications.