15 February 2009

The Ektron CMS provided the ability for a high level of interaction between various types of content. Some interaction was achieved through creating templating, but the bulk of the interaction was achieved through complex use of the Ektron API. Unfortunately, as the complexity increased, so did the number of computations necessary to render a single page. Ektron's url aliasing conflicts with built-in ASP.Net page-level caching, so I built a workaround.

The pages use the Microsoft Cache system within the master templates to simulate page caching. Since it is an in-memory cache, the cache has to be rebuilt each time the web site is restarted, or when the application pool is flushed. Overall, these highly complex pages have load times similar to static content served by IIS. This was a big technological win, and more details will be posted later.

Technologies:
Team:


blog comments powered by Disqus