3.3.
Convert Underperforming XSL Renderings to .NET
Certain operations can be completed much more efficiently in .NET than in XSL. Use Sitecore’s browser-based debugger to identify poorly performing code for migration to pure .NET.
Invoking XSL may be more expensive in .NET than executing native .NET code. If possible, certain XSL renderings, especially those which consume a great deal of resources or can only be cached under limited conditions should be converted to .NET method renderings, sublayouts or web controls. Expensive XSL code can be converted to .NET extension controls and functions.
Mark Ursino on 20 Aug 09load(): Load a piece of html into a container DOM. $.getJSON(): Load a JSON with GET method. $.getScript(): Load a JavaScript. $.get(): Use this if you want to make a GET call and play extensively with the response. $.post(): Use this if you want to make a POST call and don't want to load the response to some container DOM. $.ajax(): Use this if you need to do something when XHR fails, or you need to specify ajax options (e.g. cache: true) on the fly.
