Steve, I found that asking a cache question will clear the room pretty fast. Perhaps the mere mention of cache creates more questions than it answers and for good reason. The documentation is not that clear and there are a lot of gotchas. Anyhow here is more of my attempt to reason through the IBS fragment cache problem... Every place Response.Cache is referenced in MSDN it refers to caching an ENTIRE web page. Anytime a specific user control is referenced with fragment caching it refers to the page directive, OutputCache. When both are referenced together there is no clear distinction made between the two. From trial and error I proved, at least to myself, that Response.Cache will work with application cache but it caches all the modules (web user controls) on the entire web page not just one module. The page directive OutputCache will cache a user control but does not work with application cache. So the ugly conclusion... There is currently no way to programmatically fragment cache a module in IBS. There is currently no way to use the OutputCache page directive in IBS. There is currently no way to perform fragment caching in IBS. There is currently no way to save bandwidth for the little guy using a 28.8 modem using IBS. It’s beginning to sound pretty tragic! Somebody please chime in if you have knowledge to prove me right or wrong! Also let me know if anyone knows how to implement Response.Cache within the IBS Paradigm. At least for now, IBS and its application cache exist for the corporate and metropolitan world. Mike