title: Laravel 4 - Route::resource vs Route::controller. Which to use?
body: <p>I understand that a Resource controller can have the following methods</p>
  
  <pre><code>index
  show
  create
  edit
  store
  update
  destroy
  </code></pre>
  
  <p>Now suppose I have the following actions which need to be performed in addition to the resource actions:</p>
  
  <ul>
  <li>User attempts to log in.</li>
  <li>Admin wishes to find a user by email / first-name</li>
  <li>User requests a post by it's slug</li>
  </ul>
  
  <p>Are resource controllers useless for the above functionality? If programming an API, I obviously want the index, show, edit,create,destroy... but also the login, find, search etc...</p>
  
  <p>Is it possible to route to both types of controller? e.g.</p>
  
  <pre><code>Route::group(['prefix' =&gt; 'api'], function() {
      Route::group(['prefix' =&gt; 'v1'], function() {
          // Resource Controller
          Route::resource('posts', 'Api\V1\PostsResourceController');
  
          // Restful Controller
          Route::controller('posts', 'Api\V1\PostsController');
      });
  });
  </code></pre>
  
  <p>Or should I just forget about the resource controller and use a restful controller instead?</p>