ASP.NET MVC controllers best practice for method naming
<p>I know next to nothing about MVC so my question might look a bit basic but here it is anyway : is it a good practice to have the same name for the method returning the view and the one saving the data ? </p>

<p>I see a lot of <a href="http://www.asp.net/mvc/overview/older-versions-1/controllers-and-routing/creating-a-controller-cs" rel="nofollow">examples like this one</a> where the overloaded "Create" does both jobs. Here's a snippet:</p>

<blockquote>
<pre><code>    //
    // GET: /Customer/Create&gt; 
    public ActionResult Create()
    {
        return View();
    } 

    //
    // POST: /Customer/Create&gt; 
    [AcceptVerbs(HttpVerbs.Post)]
    public ActionResult Create(FormCollection collection)
    {
        try
        {
            // TODO: Add insert logic here&gt; 
            return RedirectToAction("Index");
        }
        catch
        {
            return View();
        }
    }
</code></pre>
</blockquote>

<p>I personnaly find it confusing when overloads do completely different things depending on which I decide to choose. So what do you think ? Is it really the "best practice" to roll that way? </p>