Hi Andreas,This is exactly why using the Command pattern a la gwt-dispatch is recommended :-)
But a Command pattern gets really annoying if you start using code splitting. GWT will load every serializer for every command (generic command interface) on startup because the generated RPC service has a reference to them.
Currently we load about 500-600kb of serializers we do not need on app startup just because of the amount of commands we have. Only solution so far would be to have multiple dispatch services each with a more specific execute method (one command interface per "application module" that has been code splitted). If you then want client side caching you would have similar issues as Andreas.
-- J.
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/-/unklLS8jut8J.
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.
No comments:
Post a Comment