Skip to content


Subversion checkout URL

You can clone with
Download ZIP
Commits on Jan 13, 2015
  1. @DamianEdwards

    Merge branch 'release'

    DamianEdwards committed
Commits on Dec 12, 2014
  1. @halter73
  2. @halter73

    Revert "Added test to verify that WindowsIdentities are usable in OnD…

    halter73 committed
    This reverts commit e1b1de6.
  3. @halter73
Commits on Dec 4, 2014
  1. @halter73

    Make Hub<T>.Clients settable for testing

    halter73 committed
    - Setting Hub<T>.Clients to null will really set it to its default value
  2. @halter73
Commits on Dec 2, 2014
  1. @halter73

    Always subscribe to all ACKs on all servers

    halter73 committed
    Prior to this fix, Groups.Add would fail to complete when there was no
    subscription configured to receive the ACK on the server Groups.Add was
    called on.
  2. @halter73

    Update Resources.resw so git doesn't annoy me

    halter73 committed
    - The WinRT client has been superseded by the portable and store clients,
      so we should probably just remove this project.
Commits on Nov 21, 2014
  1. @halter73
Commits on Nov 6, 2014
  1. @moozzyk

    YouShould(Not)AlwaysCallDispose - reverting dispoing websockets on th…

    moozzyk committed
    …e server
    AspNetWebsocket uncoditionally throws a NotSupportedException from the Dispose() method, so #ifdefing the invocation so that we only call Dispose on the client.
Commits on Oct 31, 2014
  1. @Xiaohongt
Commits on Oct 30, 2014
  1. @halter73

    Remove WebSocket prototype from mock WebSocket

    halter73 committed
    - Safari 7.1+ complains if you use a non-WebSocket object sharing the
      WebSocket prototype. HubSpot/pace#173
  2. @halter73

    Remove setTimeout from JS test

    halter73 committed
    - Previously, even the minimum timeout would take so long the connection
      would successfully start before the timeout fired.
  3. @halter73

    Avoid an uncaught TypeError which can stop the entire QUnit test suite

    halter73 committed
    - If the WebSocket transport failed to connect, an uncaught type error
      would be thrown from the modified
  4. @halter73
  5. @halter73
  6. @halter73
Commits on Oct 29, 2014
  1. @moozzyk
Commits on Oct 24, 2014
  1. @halter73

    Update Client.Store platform moniker to portable-win81+wpa81

    halter73 committed
    - Previously, when I tried installing the client package into a universal app,
      only the phone project got the additional dll with WebSocket support.
  2. @Xiaohongt

    Removed await from RedisMessageBus.Send

    Xiaohongt committed
    - The await would cause an unnecessary SyncContext.Post that would prevent
      the returned Task from completing if there was a thread blocked on the
      returned Task while holding the SyncConetext.
  3. @moozzyk

    DontDieInTheStore - handling exceptions in receive in websocket store…

    moozzyk committed
    … transport
    If an exception happened while reading a message using the websocket store transport we would not handle. As a result it would be bubbled up and would crash the user's app. The user have no way of catching this exception. The fix is to catch exceptions and report them to the user using the IConnection.Error and to close the websocket to enable reconnect logic.
    Workitem #3313
Commits on Oct 15, 2014
  1. @halter73

    Remove the JS AppDomain restart test

    halter73 committed
    - This test proved unreliable with long polling which would not always
      go into the reconnecting state if the restart was in between polls
    - The restarting AppDomain could cause other tests running concurrently
      locally or in TestSwarm to fail
    - The JS test is replaced by an equivalent .NET client functional test
  2. @halter73

    Handle transport failures occurring in the connecting state

    halter73 committed
    - In the event of any transport error prior to the init message,
      the transport should immediately stop and allow the connection to
      fall back to another transport.
    - In the event of any transport error during the start request,
      the entire connection should immediately be stopped
Commits on Oct 10, 2014
  1. @mikary

    Merge pull request #2971 from thomaswr/dev

    mikary committed
    Add performance counters to measure current connections by transport
  2. @mikary

    Merge pull request #3099 from ermontgo/dev

    mikary committed
    Allow HubConnections to be used in Crank
  3. @DamianEdwards
  4. @DamianEdwards
  5. @DamianEdwards
  6. @DamianEdwards

    Fix Code Analysis error

    DamianEdwards committed
  7. @DamianEdwards

    Merge pull request #3286 from BrandonLWhite/bug-3208

    DamianEdwards committed
    Fixed memory leak of IHub instances. This resolves #3208.  DefaultDepend...
Commits on Oct 4, 2014
  1. @BrandonLWhite
Commits on Oct 1, 2014
  1. @BrandonLWhite

    Added IUntrackedDisposable and blacklisted in DefaultDependencyResolver.

    BrandonLWhite committed
    - DefaultDependencyResolver will now no longer retain instances to IDisposables that implement the special marker interface IUntrackedDisposable.
Commits on Sep 23, 2014
  1. @halter73

    Detect slow callbacks in .NET client receive queue and trigger an error

    halter73 committed
    Since we serialize the invocations of Received callbacks in the .NET client,
    there is a real risk of deadlocks resulting from one callback blocking waiting
    on another callback to execute.
    This commit introduces a TaskQueueMonitor used exclusively by the .NET client
    to try to detect callbacks that are running long and notify the user using
    Connection.OnError that a callback may be deadlocked.
    The amount of time a callback may execute before an error is raised can be
    configured using Connection.DeadlockErrorTimeout. The default timeout is
    10 seconds.
  2. @moozzyk

    Doomed - prevent from sending a message when reconnecting

    moozzyk committed
    Previously the store `WebSocketTransport` would accept `Send` requests when the transport was reconnecting. The change to invoke `OnError()` and throw an exception if this happens - similarly to what we do in the .NET Client.
  3. @moozzyk

    RespectMe - respecting disconnect token in store WebSocketTransport

    moozzyk committed
    The store WebSocketTransport did not respect the disconnect token. Now if the disconnect cancellation token is cancelled we will not try to reconnect if the websocket gets closed and if we are already trying to reconnect we will stop doing this. Note that we don't need to register to the cancellation event since the disconnect cancellation token is cancelled only in the `Connection.Disconnect()` method which also disposes the transport which will take care of the all needed clean up.
    Also fixed a race in the WebSocketTransport.Dispose method which might lead to unwanted reconnection attempts.
    Workitem #3189
Something went wrong with that request. Please try again.