If you don't want to switch your RPC mechanism or its still too slow then you have to fetch your data in smaller chunks. For example presenting 10000 objects in a UI list does not make that much sense. Loading chunks of 500 objects while the user scrolls through the list would make more sense. Its like here in Google Groups. Loading all topics at once wouldn't work, thus they load chunks of topics while you scroll through them.
If you really need that 10000 objects from the beginning you could maybe use a RepeatingCommand and load chunks of 500 objects until you have loaded everything. That way the browser wouldn't lock up, but it will take longer to download and present the data.
-- J.
Am Mittwoch, 25. April 2012 12:17:19 UTC+2 schrieb Jacob Glusted Madsen:
Hi,We are having problems with serialization/deserialization of RPC data. This process seems to become very slow when the amount of data increasesThe problem seems to be greatest in ie8It runs faster in Crome!Does anyone have any sugestions on how to make the RPC serialization/deserialization run faster ??
Am Mittwoch, 25. April 2012 12:17:19 UTC+2 schrieb Jacob Glusted Madsen:
--Hi,We are having problems with serialization/deserialization of RPC data. This process seems to become very slow when the amount of data increasesThe problem seems to be greatest in ie8It runs faster in Crome!Does anyone have any sugestions on how to make the RPC serialization/deserialization run faster ??
You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group.
To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/YamxAlMJBd4J.
To post to this group, send email to google-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to google-web-toolkit+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
No comments:
Post a Comment