You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 14, 2024. It is now read-only.
I am trying to create a synchronous connection with NSCondition.
But when i wait for the signal, the socket calls onDisconnect(); right after a successful
connection.
I even tried with a sleep(1); and got the same behavior.
The connection is not even opened in the same thread as the sleep. Did i missed something ? Is there a way to ensure the connection to go through ?
Thanks a lot.
The text was updated successfully, but these errors were encountered:
Ok, i was completely wrong. This has nothing to do with threads.
I am actually receiving this error because i am using a custom resourceName, and in SocketIOTransportWebsocket and SocketIOTransportXHR there is no custom resourceName possible. Causing the disconnect without error.
I want to wait until the event is fired in the connection method, but the thread is locked and the client can only connect after the NSCondition timed out.
(openResetEvent is my NSCondition handler)
Do you have an idea to overcome this ?
Thanks a lot !
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hi,
I am trying to create a synchronous connection with NSCondition.
But when i wait for the signal, the socket calls onDisconnect(); right after a successful
connection.
I even tried with a sleep(1); and got the same behavior.
The connection is not even opened in the same thread as the sleep. Did i missed something ? Is there a way to ensure the connection to go through ?
Thanks a lot.
The text was updated successfully, but these errors were encountered: