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
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.comwrote:
Hi all,
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
If you exclude MVP from this conversation then it would be quite correct to
think of GWT more as a library than a framework and with that being the case
it doesn't impose either fat or thin client architecture; it is what you
make it to be.
Personally, I'd use a fat client when dealing with App
