Sean Schofield schrieb: > Paging is fine for some things but at times it seems excessive. In > our system we have a wizard where the user needs to assign a person to > a document. When you show the full 2000 users in the system its much > slower then before we went to JSF. > Is paging really the issue, couldnt it be simply a deferred rendering, due to datafetching before rendering? Pushing the whole table into ajax might be the easier solution that way you have the rest of the page rendered before the data is.
> IMO the user shouldn't see a noticeably slower GUI b/c we've switched > to JSF. Paging is a PITA in this case. I know the name I want, so > why can't I sort by last name and scroll down to it (and do it fast?) > Paging sucks in this example. > Well I think you only will get this speed with such a control if you can serve the data entirely from ram, and yes once you can do that I agree it it faster, but once you hit the db I even think this is way slower due to the bigger request burden it puts onto the db. Anyway having such a control, would be cool nevertheless ;-)
