Well, you can do the computational stuff on the server, but there is little point if all the data is available (or can be made available) on the client.
I think I would go for the term 'obese client' :-) Ian On 29 December 2010 16:05, Ross McKinnon <r.mckinno...@googlemail.com>wrote: > Hi all, > > Quick question... > > Does GWT incorporate a Fat or Thin Client-Server Architecture? Or does > it depend on the application itself. > > My view is that it is a form of hybrid as it pushes all of the client > stuff out to the client and does the heavy computational stuff on the > server. > > Whats everyone else's thoughts? > > Thanks, > Ross > > -- > 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<google-web-toolkit%2bunsubscr...@googlegroups.com> > . > 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 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.
