Can my ControllerActionInvoker be a singleton?

It doesn't seem like ControllerActionInvoker has any implementation details that require a new instance to be created for each Controller. It seems to have two properties with setters that are never used, and getters that are basically lazy references to static members.

I am considering changing the scope of my custom ControllerActionInvoker's life cycle in my ASP.NET MVC application. Is there a good reason I shouldn't do this? Is there something 开发者_如何转开发I'm missing about this class?

---

There isn't anything implicitly wrong with implementing the IActionInvoker this way.

However, there is also no implicit benefit. It depends on how you want to scope that particular component of the MVC lifecycle.