I would see it from a slightly different angle. I'll put my code on the server if one or more of these points matches:
- Algorithm is so time consuming that its impossible to implement on client side without having the browser to freeze. (UI responsiveness/speed, user experience) - I have to fetch a lot of data for computation but the result I am interested in is pretty small. (save bandwidth with respect to mobile devices) - I want to keep the algorithm private. (protect code) - GWT cant compile the code to JavaScript (GWT restrictions) So if you have a pretty complex algorithm, but its fast enough that a browser does not freeze and you don't need tons of data from your backend as input for that algorithm its totally fine to implement that algorithm on client side. Basically it all comes down to user experience. If the user experience is great, you have done it correctly. -- 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/-/Le3TW68MZ3gJ. 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.
