Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Save more on your purchases! discount-offer-chevron-icon
Savings automatically calculated. No voucher code required.
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
SignalR Blueprints

You're reading from   SignalR Blueprints Build real-time ASP.NET web applications with SignalR and create various interesting projects to improve your user experience

Arrow left icon
Product type Paperback
Published in Feb 2015
Publisher
ISBN-13 9781783983124
Length 244 pages
Edition 1st Edition
Languages
Tools
Arrow right icon
Author (1):
Arrow left icon
Einar Ingerbrigsten Einar Ingerbrigsten
Author Profile Icon Einar Ingerbrigsten
Einar Ingerbrigsten
Arrow right icon
View More author details
Toc

Table of Contents (12) Chapters Close

Preface 1. The Primer FREE CHAPTER 2. Overheating the Discussion 3. Extra! Extra! Read All About It! 4. Can You Measure It? 5. What Line of Business Are You In? 6. An Architectural Taste 7. The Three Screens – Mobile First 8. Putting the X in .NET – Xamarin 9. Debugging or Troubleshooting 10. Hosting and Deployment Index

Our single page

Whether one should strive towards having an SPA is widely discussed on the Web these days. My opinion on the subject, in the interest of the user, is that we should really try to push things in this direction. Having not to post back and cause a full reload of the page and all its resources and getting into the correct state gives the user a better experience. Some of the arguments to perform post-backs every now and then go in the direction of fixing potential memory leaks happening in the browser. Although the technique is sound and the result is right, it really just camouflages a problem one has in the system. However, as with everything, it really depends on the situation.

At the core of an SPA is a single page (pun intended), which is usually the index.html file sitting at the root of the project. Add the new index.html file and edit it as follows:

  1. Add a new HTML file (index.html) at the root of the project by right- clicking on the Chapter4 project in Solution Explorer...
lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime
Banner background image