Re: Cell Table Data Handling & Performance

On Mon, Jul 25, 2011 at 1:22 PM, BST <babusri.21@gmail.com> wrote:

Many Thanks for the input. 

The scenario is that I am not displaying more than 100 rows per page. And the pager works through 3 pages. 

Yes the Data load is on Demand, as when the user presses the next button for the 4th page I am getting another 300 rows thru an RPC. It is a plain view only table. So only after the user has paged thru the 3 pages I go for the next batch of 300.

 Also No changes or search within the table, it is view only. The table is a result of a server call for search. So I guess so far no worries :-)

CellTable caches the row values within the current page so it can pass the row values to Cells, and so it can re-render rows when needed.  When you switch pages, the row values of the previous page are dumped.

My understanding: So when I am viewing the 11 th page with 100 rows and go to the 12th page  (using an implementation AbstractPager), the rows on the 11th Page is dumped and no longer in the browser. So only 100 rows are managed by the browser even though 1100 rows of data is available with the DataProvider List. Have I got it right?

Let's say the User has paged thru about 12 pages, so there is a list of 1200 in the dataProvider list already of which 100 are being shown in a page. So when the user goes back and forth within the range of 12 pages(1200 rows) sorting or changing the display per page  to be 50 or 25 (on the client side),will the cell table efficiently manage? 

Yes, it only caches the data on the current page.  When you go back and forth between pages (even pages that you've already visited), CellTable will send a new request to the data store for the rows in range.

This allows you to control the overall caching policy in your data provider.  You can choose to cache all rows that you receive from the server in your data provider, or you could, for example, just cache a window for plus or minus 5 pages.

I guess after your reply I will be more confident in delivering the solution :-)

--

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/-/9IaeCLLTpQoJ.

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.

--
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+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.