When you start to dig deep into the differences between a single-page application and an ASP.NET Master Page implementation, you start to realize that they actually are more similar to each other than different - being that a single-page application is simply a shell page to house content pages just like a master page, except that the shell page in a single-page application does not reload or execute like a master page does with each new page request.
Perhaps the name Single-Page Application is an unfortunate name that may lead you to believe that the technology is not an appropriate choice for building web-based applications that need to scale to an enterprise-wide application that may consist of several hundred content web pages with thousands of users.
The goal of this article is to develop a single-page application that can be implemented with hundreds of content pages with all the functionality that an enterprise application needs to support thousands of users, including authentication, authorization and session state etc.
Your new post is loading...
I have not read a word of this article...can somebody translate?
*Stretch it Out*