You have some astounding performance numbers and experience. Thanks! Maybe it was a mistake, but I just started with Microsoft's .NET, ASP.NET, and IIS and no

You have some astounding performance numbers and experience. Thanks! Maybe it was a mistake, but I just started with Microsoft's .NET, ASP.NET, and IIS and no more than that as a framework. Maybe that was not so good. I had to find, download, read, abstract, and index 5000+ Web pages from MSDN -- a big delay and not so good. For the session state store, I just thought that it was an obvious, easy, routine, normal, expected little bit of programming based on TCP/IP, serialization, and collection classes. I'd heard of Redis but guessed that just reading the documentation enough to understand it and get it installed would be more work that what I did DIY. What I did was awfully easy. Yes, you have some good 5 minute solutions, but I didn't have the background to have the knowledge, infrastructure, and code that offered the 5 minute solutions -- I didn't know such things existed. No such things were clear chasing around among and reading Web pages at MSDN. Well, my session state store work is done well enough now for now and clearly easy enough for me to change to something else later if necessary. I'm learning, which was the main objective of my first post here. Thanks.