Views: 5878
Number of votes: 2
Average rating:

Initialize HTTP events in a module

EPiServer CMS 6 and Community 4 introduced a new approach to initialization, read more about it here.

We are adding infrastructure for subscribing to HTTP events in the R2 wave with the new IInitializableHttpModule interface which is defined like this:

public interface IInitializableHttpModule : IInitializableModule
{
void InitializeHttpEvents(HttpApplication application);
}

Every time a new HttpApplication is being initialized this interface will let you participate and listen to events. Do remember that this is an initializer interface, there will only be one instance of your initializer but there will be many HttpApplication instances being initialized. The use case for this interface is to able to deploy modules without adding adding an HTTP Module in web.config.

A skeleton module to use the new interface:

[ModuleDependency(typeof(EPiServer.Web.InitializationModule))]
public class MyInitialization : IInitializableHttpModule
{
public void InitializeHttpEvents(HttpApplication application)
{
application.BeginRequest += application_BeginRequest;
}

public void Initialize(EPiServer.Framework.Initialization.InitializationEngine context)
{
DataFactory.Instance.PublishedPage += Instance_PublishedPage;
}

public void Uninitialize(EPiServer.Framework.Initialization.InitializationEngine context)
{
DataFactory.Instance.PublishedPage -= Instance_PublishedPage;
}

public void Preload(string[] parameters)
{
}

void Instance_PublishedPage(object sender, PageEventArgs e)
{
//implementation
}

void application_BeginRequest(object sender, EventArgs e)
{
//implementation
}
}

Jan 27, 2011

toni
(By toni, 1/27/2011 3:14:00 PM)

Nice!
Also: adding adding ;)

Please login to comment.