On Feb 2, 8:27 pm, Dan Ox <[email protected]> wrote: > When the GWT RPC client sends a request, the 5th field is the strong > name. If you are creating your own encoded message on the server, then > you can put whatever string you want in there and, presuming you name > the RPC file with the same string, it should automatically get read in > by the code I mentioned above. Thanks. I am not parsing the client request (though from what you said maybe that is the answer) nor am I constructing one explicitly. I am only using the RPC.encodeResultForSuccess() method to take the result of a server side GWT call and serialize it a page in my application. On the server side I place this serialized data into a javascript variable in the HTML page. The GWT code executing on the client then pulls this out, deserializes it, and uses it. The purpose is to save a round trip to the server and to simplify the startup logic. My GWT client comes down with all of its data, type safe, ready to go and does not have to make a remote RPC call. I have wrapped this process with some generic methods to make it easier to use and I'm using it extensively in my app. I read about this capability in one of the google code talks (can't remember the name). But my problem remains that in order to use the RPC.encodeResultForSuccess() method from my server side presentation layer I have to either a) know the strong name or b) manually copy the file into a known location in my build. Again, I may be missing something obvious here. But I'm not sure how to do this properly. thanks, Pat --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
