aspnetcore

Commit Graph

Author	SHA1	Message	Date
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

Author

SHA1

Message

Date

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

1 Commits