Thanks both for your answers. Michael, I'm hoping to see that video. About your idea of return only data that will be visible, you are 100% right, so, in order to make this happen, I think is better to get that subset of data directly from the SQL call, than getting all data and then reduce this data to create our subset, what do you think about it? I'm not actually using neither of those strategies, but I want to do it from now on, so I would like you to guide me on how to do it the best way. Joe, I disagree with you about your first sentence, I don't think that an efficient performance would be left to personal preferences, in fact, that's what we are looking by using ajax, not only a pretty web application, but an efficient and low traffic application. About the rest, I totally agree with you and Michael, I think is better to generate our own code than rely on some generated code, although in the datagrid case, the generated code is quite simple, is just a simple html table. Another thing, is true that we can't say one way is better than the other, but we do can say, one way is more efficient than the other, so, wich do you think is more efficient? why?
--~--~---------~--~----~------------~-------~--~----~ 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/ Don't forget to read my blog at http://weblogs.asp.net/mschwarz/ The open source project is now located at http://www.codeplex.com/Wiki/View.aspx?ProjectName=AjaxPro -~----------~----~----~----~------~----~------~--~---
