Comment 3 for bug 744771

OK, imagining we scrap everything off and have all our model classes to be server side ONLY; and providing api to access every field it will be very difficult to implement the UI.

I'm not saying it's impossible, but without doing filed duplication it's going to be very messy.

For example, the admin wanting to look at the list of users would have been easy if we had a User object to be passed to the client. We would simply return a list of User objects.

However, if we are to do single requests for each field, it'll be so many queries.

Once again, a work around this would be to build a table (or any HTML representation) in the server side ServiceImpl and pass it back. This would however limit us in using client side gwt feature in building a dynamic page.

I can't really think of a better way to get around the issue of not having to pass objects to the client side.

Any thoughts would be helpful.