I just started with GWT and Eclipse and am new to Java as well - but learning. I'm trying to code some proof of concept apps for our larger project. My model is that the GWT will start about at the same time that my main application starts. The user will establish a connection at some point. Only one user will connect at any time.
The main application will enqueue status messages for delivery to the server side when requested where they will be enqueued until requested by the client. I had thought to use a timer to send the requests but now see that it is possible to for the server to push the data (Strings). I think I understand how to use the timer method and have coded a test case. I think that I would prefer to have the server push the data (after some initialization it shouldn't be frequent) but don't understand the trade offs except that it appears that using a timer is easy but the push code is much more complex. Question: Does the push model add much overhead in terms of CPU utilization or critical resources? If not I'll start to examine demonstration code that I found. I would appreciate any advice. Thanks -- 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.
