Hi, when editing large object graphs on the client-side, there are currently two problems regarding performance:
1) Entity proxies could not be modified when firing a RequestContext. A diff will be done nevertheless, which costs CPU time. There could be an annotation which marks entity proxies as immutable on the client-side and forces RF to always send the EntityProxyId. 2) All reachable value proxies on the edited data will be sent, even if the owner entity proxies did not change. This increases the payload size and could be avoided by sending only those values proxies which are reachable through actually edited entity proxies (or request arguments). There is already a todo in https://code.google.com/p/google-web-toolkit/source/browse/trunk/user/src/com/google/web/bindery/requestfactory/shared/impl/AbstractRequestContext.java#1211 Are you aware of those problems, and are they relevant enough to be taken into account in one of the next releases? Also is there a plan to add support for Maps ( https://codereview.appspot.com/6132056/.)? Regards, Stefan Ollinger -- -- http://groups.google.com/group/Google-Web-Toolkit-Contributors --- You received this message because you are subscribed to the Google Groups "Google Web Toolkit Contributors" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit-contributors+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
