have to do.

Just don't get why this isn't more important.
The control is useless unless you only ever plan to run your app from 1 server (not a farm/garden).

I mean... generally, you don't plan on a web farm all the time from day 1... you just want to code the application.  The last thing you want is to find out that after you have an application out there running with a lot of users and is time to balance it across a web farm that that you have to remove a bunch of code because "it isn't supported".

This control in general is frustrating, because I don't know why the "cache" object is used instead of the session object anyway??  Seems like you could use Session and have basically what you were trying to accomplish with "cache" while making the control compliant with Web Farms (assuming you had an out of proc session state).  Seems like a pretty easy fix to me...

Just a little silly that I have to code my own if I want a similar thing for my application on a web farm.