Frederick Cheung wrote: > On May 20, 6:23�pm, Ralph Shnelvar <[email protected]> wrote: >> First of all, thank you about the info about the tcp connection. �Can >> you point me at any additional information about that, please? >> > > Not that I can think of - it's just how people write network software
Yeah. If you need to think about the TCP connection when writing a simple Web application, you've already made a design error. > >> > One way of doing things might be for there to be a games table, and >> > pass the id of the game either in the url or stash it in the session >> > (session not so hot if this is actually going to be two tabs in the >> > same browser) >> >> When on stores it in the session, where is that stored??? Configurable within Rails. Generally cookie or database table. >> >> I am still very lost as to what a session is. �Is there a good article >> you could recommend? >> > > http://guides.rubyonrails.org/security.html#sessions > Rails generally does a good enough job of session management that you can treat it as magic. Your automated tests will take care of the rest. > Fred Best, -- Marnen Laibow-Koser http://www.marnen.org [email protected] -- Posted via http://www.ruby-forum.com/. -- 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.
