Ok, and what are the pros and cons?AFAIK you can do both server-side and client-side code with Vaadin. And GWT is used at the client-side...
Whenever you interact with the UI, Vaadin has to send a server request to figure out how the client side UI should change now. This is also true if you don't need any data from the server. E.g. if you click a button and a popup should be shown, Vaadin will do a server request when you click the button and nothing else will happen until the request completes as the response contains the information about the new UI state ( = show popup).
So the pure reaction time of your UI depends on your network quality. That's not necessarily a disadvantage but it is something to keep in mind.
However there is a Vaadin addon called Snappy that tries to reduce this dependency and I have been told that Vaadin is working on a generalization of that addon which would allow developers to decide if they want to move some UI state logic to the client so you can save server requests here and there to make the UI react faster.
You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group.
To unsubscribe from this group and stop receiving emails from it, send an email to firstname.lastname@example.org.
To post to this group, send email to email@example.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.