On May 20, 5:45 pm, Ralph Shnelvar <[email protected]> wrote:
> If Google were implemented in Rails, some controller would see the > request, process it, hand off to a view, and the view would render it. > > Basic question: When the view is rendered and sent back to the client > browser, how does the browser know what tab to render? > The data with the response will come back over the same tcp connection as the request, and that tcp connection is owned by some object that knows what to do with the data (a bit more complicated if keep-alive & pipelineing are involved but that sort of low level detail is probably just handled by the networking library you sit on top of. > > My "web server" is Webrick. > > I think I know enough Ajax to make this happen if there were only one > tab. That is, if there were only a single "user" and the result was to > do nothing more than double what the user typed in. > > I guess I'm lost as to what a "session" represents here. > 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) -- 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.
