I haven't seen anything in GWT that would predispose it to being either kind of client. Similar to Java or other more traditional development languages, you can make it as fat or thin as you want.
I might put forth the idea that since JavaScript isn't exactly great at crunching bits, it does lend one to doing the heavy lifting on the server, and therefore be more of a thin client than not, but that seems like a bit of a stretch. -Ben On Dec 29, 11:58 am, Ian Bambury <[email protected]> wrote: > 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 <[email protected]>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 [email protected]. > > To unsubscribe from this group, send email to > > [email protected]<google-web-toolkit%[email protected]> > > . > > 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 [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.
