A table whose content is populated from either a javax.faces.model.DataModel object, or a com.webmethods.caf.faces.data.ITableContentProvider object.

The Async Table pages and sorts using asynchronous requests. When the Async Table control's clientSideCache property is set to true, the table caches rows that it has retrieved from the server until the page is refreshed, or the table or a parent of the table is refreshed. You can refresh the Async Table using the refresh() method of its client-side model. You can also use the Refresh Interval control to refresh the table on a timed basis.

You can configure the Async Table to buffer in its cache rows on either side of the visible page. When the bufferMin and bufferMax properties are set to positive integers, the table ensures that at least the bufferMin number of rows are cached on either side of the visible page.

• If the minimum number of rows is not buffered, the Async Table control retrieves the bufferMax number of rows on either side of the visible page to store in the cache.
• If the bufferChunk property is set to zero (0), the Async Table control retrieves the rows as one group.
• If the bufferChunk property is set to a positive integer, the Async Table control uses multiple asynchronous requests to retrieve the specific number of rows set in the bufferChunk property

For example, an Async Table has the following property settings:

    clientSideCache=true
    bufferMin=10
    bufferMax=100
    bufferChunk=0


In this example, the Async Table displays rows 1 through 10 of 1000. When the page is rendered initially, the Async Table displays rows 1 - 10, and buffer rows 11 - 110. If the user pages forward to rows 91 - 100, these rows are in the client-side cache, and the user can display the rows immediately without an additional request. If the user pages forward to rows 101 - 110, these rows are also in the client-side cache, and the user can see the rows immediately. However, the buffer now contains less than 10 rows on the next side of the visible page. The buffer contains zero rows, so the Async Table must request rows 111 - 210. If the user jumps to rows 991 - 1000, these rows are not in the client-side cache and neither are the previous 10 rows. This requires that the Async Table send a request for the rows 891 - 1000, displaying the last 10 rows in the table, and buffering the previous 100 rows.

In this second example, the Async Table has the following property settings:

    clientSideCache=true
    bufferMin=50
    bufferMax=50
    bufferChunk=10


In this second example, the Async Table displays rows 1 - 10 of 1000. When the page is rendered initially, the Async Table displays rows 1 - 10. As the Async Table waits for the user to do something, it makes 5 asynchronous requests, each for 10 more rows, buffering 50 rows on the next side of the cache. If the user pages forward to rows 11 - 20, these rows are available in the client-side cache and can display immediately without an additional request. However, the buffer contains less than 50 rows on the next side of the visible page. The buffer contains the next 40 rows. The Async Table must request rows 61 - 70. If the user jumps to rows 991 - 1000, these rows are not in the client-side cache. The Async Table must request rows 991 - 1000 to display the requested rows. The Async Table makes 5 more asynchronous requests, each retrieving 10 more previous rows, bringing the buffer up to 50 on the previous side of the cache.

Children

javax.faces.Column, Basic Column control