Refactoring toward frictionless & odorless codeA broken home (controller)
time to read 1 min | 193 words
Originally posted at 3/30/2011

Previous, our HomeController looked like this:

public class HomeController : SessionController
{
    public ActionResult Blog(int id)
    {
        var blog = Session.Get<Blog>(id);

        return Json(blog, JsonRequestBehavior.AllowGet);
    }
}

My model is defined as:

image

Remember that the previous post we have changed the session management from the request scope to the action scope?

Well, that meant that we have just broken this code…

But can you see how?

0 comments
Tags:

Related posts that you may find interesting:

07 Apr 2011 Refactoring toward frictionless & odorless code: Hiding global state
NHibernate
10 Apr 2011 Refactoring toward frictionless & odorless code: The case for the view model
NHibernate
12 Sep 2011 RavenDB: Multi Maps / Reduce indexes
Raven

More posts in "Refactoring toward frictionless & odorless code" series:

  1. (12 Apr 2011) What about transactions?
  2. (11 Apr 2011) Getting rid of globals
  3. (10 Apr 2011) The case for the view model
  4. (09 Apr 2011) A broken home (controller)
  5. (08 Apr 2011) Limiting session scope
  6. (07 Apr 2011) Hiding global state
  7. (06 Apr 2011) The baseline