Mike, this is exactly where DTO pattern has to be used.
1. Just create a DTO which encapsulated all the objects required at startup. 2. And expose a new service, which would do all the sequential calls on the server and construct the dto and return. Remember, a server call is the most costliest operation in terms of time for the client. Coupled that with making it sequential, (adding to the startup time) its going to take ages). Note: RF btw has request batching :) Hope this helps! -- 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/-/IDnH0-4VAkgJ. 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.
