Hi,
I had to tackle with a similar problem in my webshop project - about
1000 articles with prices to load as the result of one search..
This lasted 10 to 20 seconds. RPC performance was NO problem. I've
solved this with table paging.
At the beginning I start a separate thread to fill a database cache
(JPA, EclipseLink) with all records and delay the RPC on the server,
until the requested table page is in the cache. The RPC methods for
the navigation buttons of the table (first page, prev. page, next
page, last page) all have to wait, until the relevant database records
are in the cache. My main problem was, that the most important record
for the user is rarely the first record in the search result. So I had
to optimize my cache filling thread. So the user has some seconds to
get a overview. If the article is not on the current page, he normally
pushes the "next page" button. In the meantime the cache on the server
is filled. I hope you understand my explanation.
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
