<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0">
  <channel>
    <title>Recent Posts in 'Why current_user in controller?' | Pragmatic Forums</title>
    <link>http://forums.pragprog.com/forums/59/topics/367</link>
    <language>en-us</language>
    <ttl>60</ttl>
    <description></description>
    <item>
      <title>Why current_user in controller? posted by Mike Mangino @ Mon, 14 Apr 2008 14:04:27 -0000</title>
      <description>&lt;p&gt;Nope, there&amp;#8217;s nothing that would keep this from working. I don&amp;#8217;t normally include the concept of a current user in my models because my domain model rarely involves a current user, that is more likely to be an artifact of the interface.&lt;/p&gt;


	&lt;p&gt;In this book, I decided to model the pattern of the restful_authentication plugin. Restful_authentication is probably the most popular Rails authentication plugin, so I figured it would be a well known interface to use.&lt;/p&gt;</description>
      <pubDate>Mon, 14 Apr 2008 14:04:27 -0000</pubDate>
      <guid isPermaLink="false">forums.pragprog.com:59:367:2589</guid>
      <author>Mike Mangino</author>
      <link>http://forums.pragprog.com/forums/59/topics/367</link>
    </item>
    <item>
      <title>Why current_user in controller? posted by Justin Ng @ Mon, 14 Apr 2008 03:32:20 -0000</title>
      <description>&lt;p&gt;Great book, but I had a question about the current_user stuff in Chapter 4.&lt;/p&gt;


	&lt;p&gt;My first thought is that the current user should be accessed via User.current instead of current_user in the application controller.  Is there something about how Facebooker works that this refactoring will not help us?&lt;/p&gt;</description>
      <pubDate>Mon, 14 Apr 2008 03:32:20 -0000</pubDate>
      <guid isPermaLink="false">forums.pragprog.com:59:367:2588</guid>
      <author>Justin Ng</author>
      <link>http://forums.pragprog.com/forums/59/topics/367</link>
    </item>
  </channel>
</rss>
