Hi All - Question for the board: In trying to get up to speed on the updates and improvements between the Ajax.Net and the AjaxPro.net frameworks I stumbled upon this post:
http://groups.google.com/group/ajaxpro/browse_frm/thread/e59c53bd5943ab75/4e5d7c2a1e06d227?q=onerror&rnum=17#4e5d7c2a1e06d227 which discusses a "huge memory leak" problem with the way the AjaxPro framework adds the javascript for the page to a static hashtable, _keyed on the Page object. The post even references some testing from the ASP.NET team about this. Can anyone shed some light on this please? Has this been addressed and fixed in recent newer versions? Was/is this a problem with legacy ajax applications running the Ajax.Net framework? Is the work-around posted a viable option to fix this problem? etc... thanks in advance! Kevin --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
