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 <select> 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 --~--~---------~--~----~------------~-------~--~----~ 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 rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-talk-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---