Indeed this is a discussion of architecture and design. In my case, on
the backend my data layer takes a from and a limit and rips off the
results and delivers to the client a json result. On the client, the
user can page forwards, backwards, jump to pages, and even change the
result limit to
Would you mind posting or emailing me the source code?
Thanks.
The source code to what? You've lost me a bit. I was describing how
you can do this, not describing code that I have lying around...
--
T.J. Crowder
Independent Software Consultant
tj / crowder software / com
www.crowdersoftware.com
This has digressed into a more architectural problem, which is whether the
data should be delivered in one large payload or incrementally loaded from
the server. The code I originally posted would be used to slice one large
table (already delivered from the server) into smaller tables. That isn't
That really should be handled serverside IMO. Otherwise all the data
is downloaded upon initial page call when all you need is one page
worth at that point.
For me it totally depends. You can have a *lot* more rows of data in
memory as an array of JavaScript objects without taking a
