I see no reason why making RPC calls as part of the onModuleLoad sequence (presumably from some classes it calls, but whatever) is a bad thing, in fact it's good to have these called out early, so while the code is running to build the GUI, the RPCs are off fetching data in parallel. With good design, many widgets are self-loading, regardless of whether they are created by onModuleLoad or some subsequent call. JS is single-thread, so don't worry about the data getting back before the GUI is done. I've had no problem doing this in my apps, so unless there is some actual compelling technical reason then fire away!
-- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. 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.
