-
Notifications
You must be signed in to change notification settings - Fork 213
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SRServerSentEventsTransport cannot negotiate with server #276
Comments
We use the serversentevents heavily, so I am guessing there is something we are missing. Are you saying you use SRServerSentEventsTransport directly? |
@joeldart found this bug while working on the |
@joeldart I am only use it for a test. For our debug server environment, SRWebSocketTransport and SRLongPollingTransport are working. When I use this, my colleague want to know if all of the transport are worked, so I found this issue. And I want to comfirm it. |
@chinaofmelon Got it. Thanks for the clarification |
- Found a case that if you slow down sse transport then both transports will be active causing a number of issues. Looks like we found that before - added completion block to see negotiate as well for #276
When I use SRServerSentEventsTransport, signalr always failed to connect to the server.I check the code found that block always be nil. when I fill the block, signalr work. How should I use this? And if I change this code, what's problem can be caused? The error code:
https://github.com/DyKnow/SignalR-ObjC/blob/feature-dev/SignalR.Client/Transports/SRServerSentEventsTransport.m
`
(void)negotiate:(id)connection connectionData:(NSString *)connectionData completionHandler:(void (^)(SRNegotiationResponse * response, NSError *error))block {
SRLogSSEDebug(@"serverSentEvents will negotiate");
[super negotiate:connection connectionData:connectionData completionHandler:nil];
}
`
The text was updated successfully, but these errors were encountered: