Open izhar-ap opened 9 years ago
Issue is with WEBSOCKETS when set instead of AutoTransport on Client side when ios app is connected and then logged out and connected with new user the second time connection fails. On specifying long polling it works fine.
Interesting research. What connection type are you using during this test? Is it primarily cellular or wifi? Are your connections http or are they https? I know with socket.io (which uses a similar best-transport strategy) they ended up going from long-poling and upgrading to websockets eventually to remove this initial load time, but what you're saying is that if you've set websockets it works everytime fast?
I'm having some trouble parsing the rep steps in https://github.com/DyKnow/SignalR-ObjC/issues/220#issuecomment-149809390, could you list them out explicitly?
Also is https://github.com/DyKnow/SignalR-ObjC/pull/221 related to this issue or someone else encountering the same problem?
In #221 we have reversed the Transport preference to select longpolling first but its just a quick fix we have to see why the issue is coming with default preference
Some time delay occurs in connection from 5 to 8 sec. which is not acceptable Reason The Delay Occurs in base libraries before any custom code at sever end or IOS end. On deep drilling it was found that issue is occurring in SRAutoTransport while finding best suitable transport available and when long polling is selected. it means websockets and SRServerSentEventsTransport are failing before which is causing the delay Issue is not where old release 2.0.0 is used
Quick Solution On specifying the transport layer Manually to WebSockets or LongPolling The delay is not there