As far as I know, GWT's serialization policy is about as good as you're going to get for compressing data. The only way to decrease the size of the data being sent to and from the server is to send less data. Perhaps there's a way to split up your calls so you don't need to fetch all the data at once?
However, you have to remember that unlike a traditional application, you're only sending data to and from the server, not the presentation + data like you would in a traditional application. -- Arthur Kalmenson On Tue, Mar 17, 2009 at 3:50 AM, razo <[email protected]> wrote: > > Hi all , > > Am developing an enterprise application using Gwt and am using RPC to > send a complex objects to the client ,i was wondering of what is the > best practice of serializing/deserializing objects to get the best > performance. not that my RPC request size is approximately 17 - 20 k > its very huge and cause a memory leak problem . > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
