ControllerContext

Topics: ASP.NET MVC
May 21, 2012 at 6:57 AM

I was looking into some customization of the MVC framework, and I couldn't help but notice that the ControllerContext is pretty much being passed around everywhere, for a few of these I was a little confused as to why the entire controller context was necessary, namely.

ActionMethodSelectorAttribute.IsValidForRequest and

ActionNameSelectorAttribute.IsValidName

could anyone provide me with some reasons why the entire ControllerContext is necessary, as opposed simply the requestContext, and/or the httpContext (the former being what makes sense, the latter being what i actually found being used)?