right, ok , that makes sense. But in this chapter i see that the author is avoiding using a model. Is this a common practice in rails or just a personal choice of the author? What if we want to list the users who are currently logged in our website ? That would require a model with access to the database right? So a module wouldnt be of any use since the data would be lost?
Session Model with CRUD and REST if we want to include a link for our users to check out other registered users who are browsing the website... ? On Feb 5, 11:27 pm, Colin Law <[email protected]> wrote: > On 5 February 2011 18:09, Filippos <[email protected]> wrote: > > > Hello > > > Finished reading chapter 9 and im a little bit confused. > > > 1. In the tutorial, Modules are used instead of creating a Model and > > working in a class inside a module , like in authenticating passwords. > > Wouldn't that be possible? Or is it unnecessary since we're not > > messing with a database in terms of storing data? > > Classes that do not have database storage can be in modules or models, > if that is the question you are asking. > > Colin -- 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.
