I agree with you, although I doubt that anybody is using more than 2 HttpVerbs on a standard Data input form.
While reading through the MVC source (literally 30 seconds ago) I found out that the Exception only occurs if > 1 method remains after filtering.
I’ll update the post tomorrow (it’s 0:00 in Austria)

Now, for why I wrote this post in the first place:

I wanted to have a page that lists all users of a site, and the ability to search for names:

public ActionResult List();
public ActionResult List(string query);

Since the first would just invoke GetAll() and the latter a query with a Like clause, I’d like to have those in two different methods instead of one with a if statement when using nullable types.

Anyway, thanks for your comment.

However, I’m always open to suggestions for improvement. You’ve described a neat feature, but you haven’t sold me on why it’s important or necessary.

After all, you can pretty much get the same result with:

public ActionResult Index(int? id, string name)
{
return View();
}

Also, you were innacurate about MVC. You can have more than two overloads. After all, there are more than 2 HTTP Verbs, right?

If you only use AcceptVerbsAttribute, you can have an action method per HTTP verb. There are four standard verbs, but many more than that.

Also, AcceptVerbsAttribute derives from ActionMethodSelectorAttribute. You could write your own attribute that derives from ActionMethodSelectorAttribute and implement any number of overloads of an action method, as long as one action method is selected for a given request.

MonoRail’s documentation is rather lacking and there are many questions that have to be asked before you know everything.

The graph just illustrates how much more traction ASP.NET MVC has in the community than MonoRail.

It’s like with most things MS does. They come years late to the party, but once they decide it’s going to be their way they get behind it with all their enourmous manpower and surpass them.

greetings Daniel