Is it ever sensible to attempt to persist data across a session using request.env? Say something like:
request.env['user_name'] = 'bob' I'm discussing this with the maintainer of a commercial gem (where it doesn't seem to work). My natural instinct would be to do this instead (indeed, I patched the gem): session[:user_name] = 'bob' I'm guessing that his use of request.env is derived from experience in another language (PHP?) and I just wanted to check that it wasn't some obscure, but reasonable, railsian way of doing things (that wasn't working on any of my three environments) before I went back to him. Cheers, Todd --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
