Not only would it be useful, but I strongly consider you look closely at the Redis' Hash datatype if you plan to go down this road. In our application the session is basically a small collection of keys and values (i.e.: {user_id: 7, default_timezone: 'America/Chicago', ...}
) with the entire user session stored under in a single Redis hash.
Not only does using Hash simplify mapping the data if your session data is similar, but Redis uses space much more efficiently with this approach.
Our app is in ruby, but you might still find some use from what we wrote.