Fixed Issue #501

Fixed Connect/Disconnect events not firing in IE.  Issue was browser
caching bug, but was fixed by setting the src tag of hte iFrame to
nothing.
Added src attribute to iframe to prevent caching

Fixed #501
Merge pull request #572 from NTaylorMullen/Bug-Fixes

Bug fixes
Added error handling for no transport cases

Fixed #485
Merge pull request #573 from NTaylorMullen/Issue-#485

Added error handling for no transport cases
Fixed #511 and memory leak for self hosting

The #511 fix was being caused by LongPolling never
RegisteringForDisconnect.  This was because the invocation was being
called in the DoWriteAsync method iwthin the HttpListenerResponseWrapper
when LongPolling only uses the DoWrite piece.  Moving the invocation to
the DoWrite Segment (aka the catch all for writes) fixed the issue.

The Memory leak resulted from multiple requests being called and each
registering for disconnects.  For instance, if using LongPolling
transport and user sends 100 messages there was be 102 disconnect
callbacks, 100 for the messages and 2 for the 2 connection streams.
This was fixed by re-doing how the cancellation token process was built.
Added CancellationTokenResolver whos responsibility is to manage a 1 to
1 relationship between cancellation tokens and connection id's instead
of a 1 to many.
Also renamed CancellationTokenResolver to DisconnectHandler in preparation to begin work on issue 366.
Addressed Code Review Issues

Moved DisconnectHandler from base of the server infrastructure items to
the Self.Host items.  Alleviated some race conditions and further
abstracted the disconnect process into DisconnectHandler.
Addressed more code review issues

Also sorted using directives and added xml documentation.
Fixed #511 and memory leak for self hosting

The #511 fix was being caused by LongPolling never
RegisteringForDisconnect.  This was because the invocation was being
called in the DoWriteAsync method iwthin the HttpListenerResponseWrapper
when LongPolling only uses the DoWrite piece.  Moving the invocation to
the DoWrite Segment (aka the catch all for writes) fixed the issue.

The Memory leak resulted from multiple requests being called and each
registering for disconnects.  For instance, if using LongPolling
transport and user sends 100 messages there was be 102 disconnect
callbacks, 100 for the messages and 2 for the 2 connection streams.
This was fixed by re-doing how the cancellation token process was built.
Added CancellationTokenResolver whos responsibility is to manage a 1 to
1 relationship between cancellation tokens and connection id's instead
of a 1 to many.
Fixed #215, #383 and #491

All the bugs fixed in this commit are duplicates.

Executing Javascript once the DOM yielded constant loading in some
browsers where they viewed the page as continuously loading since the
entire page had not been loaded, even though the DOM had.  Fixed this
issue by re-routing the connection.start call to the window.load event
by default but also allowing the user to overwrite the default via the
startAfterPageLoad flag.
Changed Flag name waitAfterPageLoad

From startAfterPageLoad
Addressed code review issues

Made deferral flag check more consistent.  Fixed a comment to abide by
consistency
Saved referrence to $(window)

Replaced all $(window) usages with the new saved referrence
Merge pull request #578 from NTaylorMullen/Issue-#215-#383-#491

Redirect connection.start to page load if needed
Merge branch 'master' into 1.0alpha1

Conflicts:
	SignalR.Hosting.Self/HttpListenerResponseWrapper.cs
	SignalR.Hosting.Self/Server.cs
Merge branch '1.0alpha1' of github.com:SignalR/SignalR into 1.0alpha1