
- •Credits
- •About the Author
- •About the Reviewers
- •www.PacktPub.com
- •Table of Contents
- •Preface
- •The Emperor's new clothes
- •The good old terminal
- •X server
- •Remote desktop
- •Rich clients
- •Full duplex on the Web
- •Events
- •Comet
- •Hand-rolling it all
- •Think different
- •Summary
- •Where are we going?
- •The persistent connection
- •Summary
- •Moving up one level
- •Summary
- •Getting specific with groups
- •Summary
- •Becoming stateful
- •Summary
- •Becoming private
- •Summary
- •Scaling out
- •SQL Server
- •Redis
- •Azure
- •Summary
- •Looking under the covers with monitoring
- •Fiddler
- •Performance counters
- •Summary
- •Self hosting
- •Summary
- •WinJS
- •Summary
- •Index

Chapter 9
10.Open the index.html file in the Web project, and set the Hub URL explicitly, right before the start() function when the Hub connection is called:
11.In the SignalRChat.Net project, open the program.cs file, and change the
Site URL to point to the new self-hosted server:
Both the clients should now be able to connect to the new server.
Summary
Hosting any web solution in your own process can be very useful in many scenarios; with the details in this chapter, you should be well on your way to doing just that and having SignalR be your transport for communication. With everything pretty much in place with our chat and also having all of the possible server options,
it's time to start looking at another client—Windows 8 Store applications.
[ 97 ]
www.it-ebooks.info
www.it-ebooks.info