0 votes
202 views
in Coach Views by

1 Answer

+1 vote
by
selected by
 
Best answer
Server side pagination involves exiting the Coach and run a page by page retrieval based on the total number of results and the current page number requested so there is a delay in retrieval of every page, its alternative is to load the entire data at once and display it in a client side grid which supports pagination, another alternative is to have ajax calls for each page requested by the pagination controller in the table/grid control.

It depends on what the specific scenario is before you can decide which one of the approach to use

1. If the data is not huge you can load it all at once so that the initial load may take some time but subsequent page requests will not take any time at all.

2. Server side pagination helps when you have a huge data set and you want to make the initial load time minimal.

3. Ajax based pagination takes care of both the issues initial load time since only one page is loaded at the beginning and also you dont have to load the entire data at one go.

Related questions

0 votes
1 answer 41 views
0 votes
1 answer 643 views
0 votes
0 answers 38 views
0 votes
1 answer 126 views
0 votes
0 answers 77 views
0 votes
1 answer 141 views
+1 vote
0 answers 187 views

586 questions

483 answers

87 comments

1.7k users

Dosvak IBM BPM /BAW Products, Download Evaluation
Process & Performance Tools Process & Performance Tools
Code Analyzer Code Analyzer
UI Toolkit UI Toolkit
Integration Monitoring Integration Monitoring
Welcome to BPM Tips Q&A, Community wiki/forum where you can ask questions and receive answers from other IBM BPM experts and members of the community. Users with 2000 points will automatically be promoted to expert level.
Created by Dosvak LLC
Our Youtube Channel
...