Justin, If you use some javascript to provide additional administrative capabilities, doesn't that confuse non-admin users? Is it still possible for a logged in administrator to view something how a normal visitor to the site would see it? The first (CMS) Rails app I've build used this Restful style, but this meant that a logged in administrator saw the ArticlesController#show action way different than a normal user, requiring the administrator to open another browser to see how his article would be shown on the actual website. By using an Admin namespace this problem was solved easily.
- Matthijs On Tue, Dec 2, 2008 at 3:55 PM, Justin Reagor <[EMAIL PROTECTED]> wrote: > On Dec 2, 2008, at 9:18 AM, avd wrote: > > What's a good strategy for admin? > > > Most of the application I am writing nowadays are doing without a > segregated admin interface all together. > Using REST, I simply define controllers which are dual-duty. Most of my > apps are mostly GET for the public facing sites, and authentication > controlled POST/PUT/DELETE or edit GETs on top of public facing views. I > simply use Javascript/jQuery as a means of providing administrative > capabilities on top of what the user generally sees. Similar to how Soup.io > works, with their admin interface. > > I have also seen completely separate administrative applications that use > authenticated REST APIs on the public facing app. > > Other then that, there is the tried and true, Admin:: namespaced > controllers routed to /admin type stuff, which is more prevalent at my > day-to-day Rails job. > > :: Justin Reagor > :: [EMAIL PROTECTED] > > > > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "merb" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/merb?hl=en -~----------~----~----~----~------~----~------~--~---
