Richard, Marnen is absolutely right about his suggestion.
One of the most beautiful aspects of developing in RoR is the fact that there's almost a plugin/gem that you can install and use very easily for every need you may have for a webapp. (among other features/advantages) RoR is know for the development speed you can achieve. Using the right plugin/gem for a specific task is one of the multiple factors that allows you to develop at an amazing speed. Authlogic, in this case, is VERY well tested and uses in many sites. I used to use RestfulAuthentication, but I switched to Authlogic since is much cleaner and easy to understand. If you're learning RoR and you want to explore possibilities, install Authlogic and try to understand it's inner workings. You'll be gaining a lot of time and also you'll see how a very good plugin is developed. -- Mis mejores deseos, Best wishes, Meilleurs vœux, Juan Pablo ------------------------------------------------------ http://www.twitter.com/eljuanchosf 2010/7/5 Marnen Laibow-Koser <[email protected]> > RichardOnRails wrote: > > Hi Marnen, > > > > Thanks for your response (especially since you posted with an > > iphone :BG) > > > >> Beware of following any Rails book that old. > > But I should be able to adapt old stuff to run in a fairly current > > Rails version (mine's 2.3.5) > > Do you really want that hassle? Particularly since you're still a > relative beginner in Rails? I'd *really* advise against this -- you'll > probably get shown obsolete ways of doing things. > > > > >> And don't bother writing your own authentication code. Just use > Authlogic and have done with it. > > I'd rather add code to my app that I can test rather than blindly add > > code that hasn't been perused as carefully as code bless by the core > > Rails team. > > What makes you think it hasn't been tested? What makes you think the > Rails core team has a monopoly on good testing? In fact, Authlogic has > been well tested and is very widely used. If you want to check its test > suite, you are welcome to do so. > > Don't reinvent the wheel. > > [...] > > Do you care to offer me any suggestions? I'd be most appreciative. > > Part of being a good Rails developer is knowing when to use a plugin and > save yourself some work. In your case, since there's a good plugin for > the exact things you're doing, you should absolutely use it. > > > > > Best wishes, > > Richard > > Best, > -- > Marnen Laibow-Koser > http://www.marnen.org > [email protected] > > Sent from my iPhone > > > -- > Posted via http://www.ruby-forum.com/. > > -- > You received this message because you are subscribed to the Google Groups > "Ruby on Rails: Talk" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]<rubyonrails-talk%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/rubyonrails-talk?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" 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/rubyonrails-talk?hl=en.
