Re: GWT - Thin or Fat Client

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 Engine where I'd avoid rendering html on the server altogether and instead render html strictly via GWT on the client. I'd also reserve all my http requests for strictly data io and security. This is a very fat client and very thin server model but it works very well on App Engine.

If I were targeting tradition web servers I'd have a more balanced approach.

Jeff


On Wed, Dec 29, 2010 at 11:05 AM, Ross McKinnon <r.mckinnon89@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-toolkit@googlegroups.com.
To unsubscribe from this group, send email to google-web-toolkit+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.

--
Jeff Schwartz

--
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-toolkit@googlegroups.com.
To unsubscribe from this group, send email to google-web-toolkit+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.