You must have in some points share data (in your case), if you want N clients see same things. So a DB is fine. If you don't use GWT you have the same problem.
Think that GWT compile to javascript, so if you make singletons, are singletons per tab in browser. Juan. 2011/10/6 David Illescas <[email protected]> > I am really interested in the GWT technology and would like to learn > more. I have the following problem. > > I want to run a simulation on the server, such that two separate > clients accessing that simulation through a browser will see the same > simulation. With GWT, I am not sure how this is done, since two > clients seem to result in two separate generated server instances(??) > with no sharing of data. I want to avoid having two separate > simulations running because two clients are accessing the server; > there should only be one, which both clients look at. > > The only way I can of to share data between clients is to maintain > state in a database. Then the clients would simply receive data from > that shared database, and the data displayed on both client would > match. Are there better ways? > > -- > You received this message because you are subscribed to the Google Groups > "Google Web Toolkit" 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/google-web-toolkit?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" 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/google-web-toolkit?hl=en.
