# Select and session

**URL:** <https://www.ruby-forum.com/t/select-and-session/128177>\
**Category:** Rails\
**Created:** [February 5, 2008, 5:00pm UTC](https://www.ruby-forum.com/t/select-and-session/128177 "2008-02-05T17:00:06Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![kdonn](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/k/db5fbb/32.png) [@kdonn](https://www.ruby-forum.com/u/kdonn)\
**Post date:** [February 5, 2008, 5:00pm UTC](https://www.ruby-forum.com/t/select-and-session/128177/1 "2008-02-05T17:00:06Z")

</div>

I’m trying to get a decent design for handling a notion like queues in  
Netflix. On Netflix each user can have multiple movie queues. The  
user selects the queue he wants to work with from a dropdown at the  
top of any page and the entire session is then restricted to that  
queue.

It seems clear that something like queue\_id would go in the session,  
but how would you construct, say, a to map to  
session[:queue\_id]? Or would you? All of the select builders seem to  
want to operate on a member using the dot accessor. I realize I could  
cobble something up that maps @object.method to session[:queue\_id],  
but this feels like I’m fighting Rails. Am I missing something? Is  
there a more natural way to go about something like this?

Thanks,  
Kevin Donn