I simple search controller that stores search history, should I use resource routing or non-resource?
        Posted  
        
            by 
                vfilby
            
        on Stack Overflow
        
        See other posts from Stack Overflow
        
            or by vfilby
        
        
        
        Published on 2011-01-14T17:37:33Z
        Indexed on 
            2011/01/14
            17:53 UTC
        
        
        Read the original article
        Hit count: 278
        
I am learning rails and am toying with a simple web-app that integrates with flickr to search photos based on user given criteria and store the query in a search history table.
I am seeking the best or 'rails' way of handling this. Should I setup a controller and non-resource routes that handle the search and store the data in a custom table; or should I create a resource for queries with a resource route and an additional path for search?
© Stack Overflow or respective owner