aspnetcore/client-ts/Microsoft.AspNetCore.Signal...
Pawel Kadluczka e31fc1e57d Closing transports with error if hubs cannot be created
- Preventing from closing long polling transport with 204 in case of
error
- Reporting an error to the client if WebSocket was not closed normally

Note in case of ServerSentEvents it is not possible on the client to
tell the difference between when the server closed event stream due to
an exception or because the client left OnConnectedAsync. In both cases
the client sees only that the stream was closed.

Part of: #163
2017-05-31 16:29:28 -07:00
..
Common.ts
Connection.ts Make the http end points more resty (#470) 2017-05-19 23:37:17 -07:00
Formatters.ts
HttpClient.ts Make the http end points more resty (#470) 2017-05-19 23:37:17 -07:00
HubConnection.ts Fix #324 by adding streaming support to the server (#461) 2017-05-31 09:10:20 -07:00
IConnection.ts Allowing passing ITransport to start 2017-04-27 09:50:14 -07:00
ISignalROptions.ts
Message.ts
Microsoft.AspNetCore.SignalR.Client.TS.csproj Fix #324 by adding streaming support to the server (#461) 2017-05-31 09:10:20 -07:00
Observable.ts Fix #324 by adding streaming support to the server (#461) 2017-05-31 09:10:20 -07:00
Transports.ts Closing transports with error if hubs cannot be created 2017-05-31 16:29:28 -07:00
gulpfile.js Fix #324 by adding streaming support to the server (#461) 2017-05-31 09:10:20 -07:00
index.ts
tsconfig.json