> > > > scalability is important for me. I want to make strong use of server push > once I have a working skeleton. For example, I would like to push chess > moves to all clients that are currently watching a chess board: The two > players and all visitors. There are other chess servers that do this (e. g. > www.schacharena.de), and they have thousands of users. It would be hard > to believe that they use a technique with one open/waiting request per > client. (BTW: Can one determine which technique is used there from the > outside?) >
You can use Chrome Developer Tools and let it display the server requests. Looks like they load a .php page in an iframe that reload itself every 5 seconds. If the opponent has done a move the .php page contains some JS code to update the chessboard. If you dont need nearly real-time feedback from your server thats the easiest solution. In GWT terms this would be a Timer that calls your service every x seconds. An alternative to Atmosphere is Errai for GWT (HP: http://www.jboss.org/errai / Docs: http://docs.jboss.org/errai/2.1.0.Final/errai/reference/html_single/#sid-5931263) -- J. -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/ODzcpr2E-QoJ. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
