I think it depends on what the user needs and how fast he need the data. I always have the data for the first page already written in the HTML code, then, when window.onload is fired I load the next page. If the user is switching to the next "page" I load the third page, so I have always the next data in memory. I never load all the data to the client.
Regards, Michael On 4/17/06, roni schuetz <[EMAIL PROTECTED]> wrote: > > on my server i host e.g. 3000 rows with data i need on the client. all > data together is something around +/- 300 - 800k. > > so i developed a routine which calls the server and receiving always > more data which I add automatically to the client. once i have all data > at the client side i can spot to make request. > > the golden question is, how much k should i return on every call? > > kind regards, > roni > > netrsc.blogspot.com > ----------------------- > > > > > -- Kind regards, Michael Schwarz Microsoft MVP - Most Valuable Professional Microsoft MCAD - Certified Application Developer http://www.schwarz-interactive.de/ mailto:[EMAIL PROTECTED] --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ajax.NET Professional" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/ajaxpro The latest downloads of Ajax.NET Professional can be found at http://www.ajaxpro.info -~----------~----~----~----~------~----~------~--~---
