You can either drive a nail using hammer or break some one's head! It really depends on how you use the tool; be it the hammer or gwt.
as far as million access is concerned, it completely depends on your server if it can handle that load or not. Look into your server side code, server infrastructure, network limitations, etc. In your client code you should avoid unnecessary server calls. Or atleast try to club multiple calls into one(if practically possible). As far as sluggishness of code is concerned for big size apps, you should divide your app into modules, use code splitting, etc. If you compare gwt app with jsp based app: - jsp app will make server trip for every user application. example multiple paged data table. - data being transferred between client and the server is more in case of jsp, as the entire page has to reload. - gwt app is usually single page based. Server calls are only made for data. - gwt app can execute most logic on client side and use server only to persist or fetch data. - In a nutshell, a well written gwt app will always reduce your server trips and amount of data being transferred when compared to traditional jsp/struts based applications. If you compare gwt to other js based toolkits, they all behave similar as far as client to server communication is concerned. gwt only makes life simple for the developers. Rakesh Wagh On Jun 19, 7:44 pm, manish kumar <[email protected]> wrote: > Hi, i have gone through many articles on web and found that GWT is not > good for an application that has million users access simultaniouly. > Is that really true? If not then what should i do make it accessible > by million users?Is that really tough job in GWT? -- 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.
