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.
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. Of course, this is just MO. Sean On 4/19/06, Werner Punz <[EMAIL PROTECTED]> wrote: > Sean Schofield schrieb: > >> So, +1 for a SoC project on this component; but for sean it may come too > >> late :) > > > > Yes too late for now but I could use it in the future. I can think of > > many situations where this would be helpful. IE 6.0 adds to the > > already slow process. It only takes 500 + rows with a few columns of > > components and things get noticeably slower then without JSF. > > > Sean, I am not sure if a dynamic scroller really eases the burden that > much, it looks cool, but thats it, in my opinion a real paginable data > model on top of the already existing jsf table is the better option, way > less burden on the server and in the end I think the response speed and > is way better and the load on the server way less. > > If you simply only load one page per time or do 5-6 chached pages the > results especially with an underlying db which allows proper pagination > (most do nowadays) are way better. > >
