tags:

views:

29

answers:

0

It struck me this morning that the ASP.NET pipeline could actually be quite useful for front-side aspect oriented programming, hooking into requests and responses to 'inject' processing into a set of resources requested, e.g. calling a method for each page when requested, instead of deriving each of the target pages from a base that does the same work.

This would have the advantage of the 'outside' processing being done to be made optional, or dependent on build configuration. Applying a set of diagnostic routines across a set of pages could be quite intrusive and invisible to the normal page life cycle and end user.

There are many articles etc. on some aspects of this, e.g. logging, but I would like some recommendations for more general papers and other resources on using this as a broad spectrum pattern.