Honey,

are you aware that DotNetNuke already provides a lot of caching including module output caching, which means that rendered output of any non-personalized module can be cached for a configurable time, which should significantly reduce the effort to display the page - I am not sure, how  much your module is able to add on top...

Sebastian, I am fully aware of the extensive caching facilities provided by DNN to modules.

And I must say, my module is NOT a replacement for that. Rather, it is built on top of DNN's caching capabilities as the tab's content is cached through DNN's own DataCache .

However, even with Module caching enabled for all modules on a page/tab, the process of loading up the skin, together with many other routine tasks DNN performs for a request are redundant if the content is not chaging between requests. This is where my module comes in. Instead of whole life-cycle, and individual look-ups for each module's content, a single look-up for the entire page/tab is enough for the request to be served.

What's more, modules perform caching according to their internal logic, with no admin control over it. This tab caching module allow admins a more precise control over which and for what time the content is cached.