I work on a project with really a lot of graphical data displayed on a HTML5 Canvas. We use GWT RPC (currently we version GWT 2.5) to transfer collections of many many small objects representing geometry details from server to client. Overhead on such data that comes with GWT RPC is so big that we have serious memory issues on a server side. So I have a question is there a better way to handle this: Option 1) Maybe double serialization to reduce number of classes that will have GWT RPC overhead. So serialize one transfer object using GWT RPC that consists from serialized data and than on client side deserialize data manually? Is there any good serialization that I can use on a client side? Option 2) Are there any other GWT compliant transfer technology which will handle a lot of small objects better (lower overhead)? Option 3) GWT Comet, etc. What do you recommend and what are the factors we should consider?
Adam -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout.
