Update:
1. Handlers namespace and HandlersMarker
The HandlersMarker is a static type used to indicate the root of the Handlers namespace.
2.)
Basic Names
<HTTP VERB>Handler (e.g., GetHandler)
The basic handler convention uses the current route definition and applies the appropriate HTTP constraint. So if you had a GetHandler under the Posts namespace, you would have: “posts/ (GET)”. Not helpful in this situation, but useful in others.
Route-contrained Names
<HTTP VERB>_<PropertyName>_handler (e.g., get_Year_Month_Title_handler)
When using this naming scheme, the HandlersUrlPolicy will apply route inputs and constraints to your route to build up pretty urls like our example from above:
posts/2011/7/hello-world
The idea now is to have a Handler, input model, output model, and a view within the same namespace. Since the namespaces are used to make up the routes, you should be able to find these fairly easily.
How do I use this?
This is part of FubuMVC.Core. As I mentioned earlier, the convention uses static types as a basis for determining the root namespaces for the routes. The extension method for applying this convention takes in a params Type[] markerTypes which allows you to pass in the types used to indicate these roots. You can take a look at the tests to see it in action.
Of course, an example would be (from within your FubuRegistry):
ApplyHandlerConventions<MyHandlerMarker>()