How about caching results on the client side? I think that can save server roundtrips. I mean storing results by keys on an javascript object. Keys can be made of the name of the method and the arguments sent (I guess it's implemented that way on the server). I think it's quite easy to implement and can save lots of roundtrips. Of course, it means adding another parameter to the function or a property such as:
Namespace.Function(param1,param2,callback,isCached) or Namespace.Function.IsCached=true | false; or so. This will enable users to decide whether they want a refreshed data or a cached data (in case this data has been already recieved). Thanks. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
