Many people using JPA/JDO or similar on the server-side already have DTOs and copy things from their entities to/from DTOs to bridge GWT-RPC and JPA/JDO. RequestFactory is not much different, except it does the "copying" part for you, and it adds better performance (serialization/deserialization on the client-side; partial graphs on server-to-client, and diffs on client-to-server), seamless upgrades (you're not required to update your clients when you change the server; and if you change contexts/proxies in "compatible" ways, you can live with "older clients" and up-to-date ones at the same time, no more "the app has been updated, please reload (and lose your work at the same time)"), and a few hooks (ServiceLayerDecorator).
-- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/E0NCjHtsx1sJ. 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.
