Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP
tag: 0.5.3
Commits on Aug 22, 2012
  1. @DamianEdwards

    Build changes

    DamianEdwards authored
     - Don't build docs for normal build
     - Fix build versioning
     - Delete build folder before build
  2. @DamianEdwards

    Made JS hubConnection API consistent with .NET but in JS style.

    DamianEdwards authored
    Updated MouseTracking sample to use new hubConnection API.
Commits on Aug 21, 2012
  1. @DamianEdwards
Commits on Aug 19, 2012
  1. @davidfowl
Commits on Aug 18, 2012
  1. @davidfowl
  2. @davidfowl
Commits on Aug 17, 2012
  1. @DamianEdwards
  2. @davidfowl

    Bumped version to 0.5.3.

    davidfowl authored
Commits on Aug 14, 2012
  1. @davidfowl

    Updated NuGet.exe.

    davidfowl authored
  2. @davidfowl

    Made changes to Error handling in client

    davidfowl authored
    - Make SetHttpResponse internal.
    - Use Stream.CopyTo in .NET 4.0
  3. @davidfowl

    Merge pull request #585 from SignalR/Issue#515

    davidfowl authored
    Added custom SignalR error handling capability - Fixed #515
Commits on Aug 13, 2012
  1. @NTaylorMullen

    Modified inline comments

    NTaylorMullen authored
  2. @NTaylorMullen

    Pointed unit test url to new URL

    NTaylorMullen authored
    The prior URL was pointing to localhost and if an IIS server was not
    running the machine would actively refuse the connection, resulting in a
    failure of the test (not a 404).
  3. @NTaylorMullen
  4. @NTaylorMullen

    Addressed PR comments

    NTaylorMullen authored
    Made the SignalRError object disposable to assure no memory is leaked
    via the HttpWebResponse associated with WebExceptions
Commits on Aug 9, 2012
  1. @NTaylorMullen
Commits on Aug 8, 2012
  1. @NTaylorMullen

    Added custom SignalR error handling capability

    NTaylorMullen authored
    Fixed #515
    
    Created an ErrorExtensions class to add a "GetError" capability to
    Exceptions.  GetError returns an error of type SignalRError which
    unwraps and pulls unique attributes out of a thrown exception to expose
    essential pieces to errors.
  2. @davidfowl

    Fixed url creation when using custom query strings when using HubConn…

    davidfowl authored
    …ection.
    
    - Added 2 more overloads to the HubConnection ctor to support using the default url.
    - Added test.
    
    Fixes #581
Commits on Aug 7, 2012
  1. @NTaylorMullen

    Unwrapped thrown exceptions

    NTaylorMullen authored
    Developers were getting wrapped exceptions which were not very
    distinguishable and required a lot of digging to pull out the base
    exception which is the most relevant piece.
  2. @davidfowl
Commits on Aug 4, 2012
  1. @davidfowl

    Made some tiny optimizations to the DisconnectHandler.

    davidfowl authored
    - Only get connection field once in initialize
    - Made CreateToken private.
    - Sorted usings.
  2. @NTaylorMullen

    Merge pull request #578 from NTaylorMullen/Issue-#215-#383-#491

    NTaylorMullen authored
    Redirect connection.start to page load if needed
  3. @NTaylorMullen

    Saved referrence to $(window)

    NTaylorMullen authored
    Replaced all $(window) usages with the new saved referrence
  4. @NTaylorMullen

    Addressed code review issues

    NTaylorMullen authored
    Made deferral flag check more consistent.  Fixed a comment to abide by
    consistency
  5. @NTaylorMullen

    Changed Flag name waitAfterPageLoad

    NTaylorMullen authored
    From startAfterPageLoad
Commits on Aug 3, 2012
  1. @NTaylorMullen

    Fixed #215, #383 and #491

    NTaylorMullen authored
    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.
  2. @NTaylorMullen

    Fixed #511 and memory leak for self hosting

    NTaylorMullen authored
    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.
  3. @NTaylorMullen

    Addressed more code review issues

    NTaylorMullen authored
    Also sorted using directives and added xml documentation.
  4. @NTaylorMullen

    Addressed Code Review Issues

    NTaylorMullen authored
    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.
Commits on Aug 2, 2012
  1. @NTaylorMullen

    Also renamed CancellationTokenResolver to DisconnectHandler in prepar…

    NTaylorMullen authored
    …ation to begin work on issue 366.
  2. @NTaylorMullen

    Fixed #511 and memory leak for self hosting

    NTaylorMullen authored
    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.
  3. @NTaylorMullen

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

    NTaylorMullen authored
    Added error handling for no transport cases
  4. @NTaylorMullen
  5. @davidfowl
  6. @NTaylorMullen
Something went wrong with that request. Please try again.