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
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.