Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

1
  • The problem is that the page is being presented to the user regardless of whether you have access to that piece. So unless you are willing to have duplicated views, the controller has no possible routing choice that hides that part. However if you were using a component-based MVC system, then this logic would absolutely go into the controller. But very few web frameworks use component-based MVC, that's an idea you more often find in interactive applications. Commented Mar 9, 2011 at 16:40