Bob Vawter did a presentation during the Google I/O conference that addressed an issue similar to this.
Rather than using a static host page, and making RPC calls at startup, you could use a JSP or servlet, and embed the initial data right into the page to be parsed at startup, no additional HTTP round trips required. http://sites.google.com/site/io/resource-bundles-and-linkers-in-google-web-toolkit have a look at the presentation slides, and maybe even watch the video. It is a great technique for situations such as this. -jason On Aug 28, 2008, at 1:58 PM, walshms wrote: > > Let me first start out by saying that I fully understand the reason > why GWT doesn't include any mechanism for synchronous RPC calls. What > I'm curious about is how someone can initialize common data structures > that don't change often but need to be returned via RPC calls. I'm > basically trying to implement a caching scheme. The rest of the > application depends on the these common data structures being != null, > but parts of the application can't be initialized until the RPC > returns. > > So, do people do I have to change the way the app starts by making a > call to continue loading the app in the callback of the "initializer"? > > Is there a less invasive way a similar caching scheme can be done? > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
