Leaks will be the problem even if you have more than one page. If leaks
happens then it will stay there even if you navigate to other page. Until
you close browser.
Here is why it's not the best choice to have single page (url)
1. People like to put pages into their favorites.
2. People like to send links.
3. People like to hit back button
with 100% AJAXyfing application you will prevent people from using every
feature they got accustomed to.
It will be a shooting yourself if it's an Internet application. More
tolerable if it's Intranet application.
I can tell from experience that even pure ASP.NET with their only POST way
of submitting the form is a big problem in Internet application. My
customers simply do not like that when they click "Back" button they get "Do
you want to resubmit data" warning from IE.
Just stick with a reasonable mix of AJAX and regular ASP.NET development.
George.
"news.microsoft.com" <no***@nowhere.netwrote in message
news:Og**************@TK2MSFTNGP03.phx.gbl...
I'm strongly considering abandoning the one-physical-file-per-page model
and going with an arcitecture that simply loads content from classes
dynamically. There will be only one page that a user will go to, and all
variation from navigation will come from AJAX calls to load and replace
content in a main frame.
... so my concern with this is, perhaps the browsers will leak memory or
do something obscurely wierd with enough loading and unloading of controls
client side. Has anyone else tried this approach, have any warnings to
share about doing things this way?
Paul