On 07/12/2011 02:02 PM, ses wrote:
Firstly I'm coming from a Java EE background and building up my Rails
knowledge slowly in my (relatively limited!) free time, so apologies
if this is rudimentary stuff.
The common pattern for user sessions seems to be something like
'session[:id] = user.id' in the controller and
'User.find(session[:id])' in the view.
However its also possible to just set an instance variable once a user
has logged in, e.g. '@id = user.id'. Due to some rails magic the
instance variable of the controller gets passed to the view, thus
facilitating a kind of session persistence. I'd hazard a guess at
saying this is probably bad form but due to not fully understanding
how the instance variable is available I'm not sure.
What's the general consensus on this?
The real experts have already weighed in on this but I thought I would
make this one comment.
ROR is in most regards stateless so while an instance variable like
@user is fine to communicate from controller to view you will have to
use the session variables to communicate from one controller invocation
to the next.
Norm
--
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.
