I don't really think that that would kill the server neither the client. However, it is also right that javascript that runs in a webbrowser is not the best platform to do floating arithmeticalcomplex calculations. You should also think, that although it is something normal that a client have a dual core or something mor powerfull, it is also typical that they have hundreds of other processes or applications running in it.
In any case, the first I would try, is to run this calculations in the most possible simple javascript, also without gwt (just native js without any other kind of framwork) and see what happens then. Maybe the compiled code is not the best optimitzation for such a calculation. Good luck ;) al On 18 March 2011 02:31, csillag <[email protected]> wrote: > On márc. 18, 02:25, joe kolba <[email protected]> wrote: > > Why do you have to do it on the client side? why not just do all of your > > processing on the server side and send the client the results. > Because I do not want to kill the server; the clients can take care of > themselves. > > > Not every client is going to have a machine that can do heavy > calculations > Even tablets are getting dual core these days, so I don't think this > is going to be a problem. > > > and they might actually be using.... IE > Well, hopefully not for long. > > Best wishes: > > Csillag > > -- > 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.
