Hi Rick, In my experience RPC is very efficient - I have a 100 or so objects serialising over the wire in less than 50ms, with simpler structures taking even less time. Something that returns just a long should complete in no time at all. Have you tried adding some timing logic to the server code that produces that long value? What timings do you get if you just return a hard long value? Using a HTTP proxy like Charles (http://www.charlesproxy.com/) will shed some light on the size of the RPC calls being made and will provide some more precise timings.
Good luck, Chris. On Feb 6, 9:08 am, Rick <rick4...@gmail.com> wrote: > Hi > > I am using Java as server so I used RPC calls. The thing worrying me > is the efficiency of RPC call. I just write a simple method getValue() > on server which returns a long value. When I called it from client, it > is taking 1 second to go to server and then come back. This 1 second > time is pinching the performance of my application and I can't afford > it. Can any one suggest what improvement should be done so that this > time get reduced. > Any suggestion in this regard will be highly appreciated . > > Thanks and reagrds > > Rick --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to Google-Web-Toolkit@googlegroups.com To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/Google-Web-Toolkit?hl=en -~----------~----~----~----~------~----~------~--~---
