Well, that is a good idea - however, it wastes ram even more than what I listed above. Each time a page was loaded that JS file would be re-added as an asset and the old JS variables would problem still persist in memory.
On Dec 8, 11:32 am, aowie <[EMAIL PROTECTED]> wrote: > One way I have seen do a good job with this, is to split up the js > related to each ajax call into their own files. So if you have an AJAX > call for login & one for registration, then you have a complimentary > js for each of those. You can then load the js how you want (I use > Assets library) after the AJAX call is completed. The new DOM will be > loaded and then the external js fires and recognizes the newly added > DOM.
