Ralph Shnelvar wrote: > >>> (2) The client issues an asynchronous request (perhaps, an XHR) which >>> gets fulfilled when the server detects that there has been a change in >>> some player's data. >> >> Impossible. That means the server will block till it has new data, which >> means the client will be stuck, waiting for a response from the server. >> >> Or do you mean that the client simply polls periodically, and if the >> server has no new data, it just says so? > > Why would the client block? It's an asynchronous request. > > Isn't that the point of an asynchronous request ... not to block?
You're right, my mistake. However, there's one other thing you should be aware of. Unless something has changed recently, most browsers allow only a fairly small number of simultaneous HTTP connections. Having a persistent server connection will tie up one of those slots. 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.
