Re: GWT server design
Gwt is client side, so it's just totally depends on how many numbers of request you'll do from your gwt application to your server. You can even have no request at all, just the first download of the application. On 9 juil, 20:45, Xsuperstore wrote: > Hello. > > I am new in the GWT word, I have some questions about server resource > design. > > Estimate of CPU & MEN compared to LAMP in Linux? > > I mean, for high traffic sites (2-5) users/day the is some > estimate/recomended hardware resources design? > > thanks in advance! -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to google-web-tool...@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
Re: GWT server design
Hi, in general a full AJAX web application (as GWT is one) do generate much less load on the server then classical web technology which are rendering a complete gui on each request. My estimates let expect that a server could drive 10-50 time more clienta when using GWT. Stefan Bachert http://gwtworld.de On 9 Jul., 20:45, Xsuperstore wrote: > Hello. > > I am new in the GWT word, I have some questions about server resource > design. > > Estimate of CPU & MEN compared to LAMP in Linux? > > I mean, for high traffic sites (2-5) users/day the is some > estimate/recomended hardware resources design? > > thanks in advance! -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to google-web-tool...@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
