@kichalla and I have discussed this issue also on http://aspnetwebstack.codeplex.com/discussions/399311. Today, you need to jump a lot of hoops to provide a custom IActionResultConverter implementation because the HttpActionDescriptor has a deep knowladge about the ActionResultConverters (see the virtual ResultConverter property of HttpActionDescriptor).
It would open up lots of flexibilities if custom IActionResultConverter implementations can be injected through the DI as a service or based on rules (just like as it is with HttpParamaterBindings today).
Comments: One other place where I would like to insject custom IActionResultConverter impl. would be to support "Prefer: return-minimal" which is not an official standard yet. I can still do that with a filter or message handler cleanly but it wouldn't be as efficient as handling it with a custom IActionResultConverter impl.
It would open up lots of flexibilities if custom IActionResultConverter implementations can be injected through the DI as a service or based on rules (just like as it is with HttpParamaterBindings today).
Comments: One other place where I would like to insject custom IActionResultConverter impl. would be to support "Prefer: return-minimal" which is not an official standard yet. I can still do that with a filter or message handler cleanly but it wouldn't be as efficient as handling it with a custom IActionResultConverter impl.