About hub.connect on windows run as blocking mode on uWebSocket about usockets HOT 5 CLOSED

It blocks on DNS lookup, that's the only thing blocking. It's a valid issue for uSockets too, I haven't solved it yet. DNS lookup should happen in a thread pool.

from usockets.

Thank you for quick response, I changed my design to use uws in multithread because I found it don't work for creating multi group and make connect calls, only last connect call works.
It works well in each thread for 1 hub. Thank you again!

from usockets.

You shouldn't hack with threading. If you require nonblocking DNS lookup then do that part yourself with a third party library and pass the IP to connect

from usockets.

the main problem for single thread is: below code only connect to url2 will work fine, no callback recieved from url1, is this a bug? thank you!

sample code:
hub_ = new Hub();
group1 = hub_->createGroup();
group1->onConnection([&](WebSocket *ws, HttpRequest req) {xxx});
group1->onError([&](void * self) {xxx};
group1->onDisconnection([&](WebSocket *ws, int code, char *data, size_t length) {xxx});
hub_->connect(url_1, nullptr, {}, 5000, group1);

group2 = hub_->createGroup();
group2->onConnection([&](WebSocket *ws, HttpRequest req) {xxx});
group2->onError([&](void * self) {xxx};
group2->onDisconnection([&](WebSocket *ws, int code, char *data, size_t length) {xxx});
hub_->connect(url_2, nullptr, {}, 5000, group2);
hub->run();

from usockets.

Well since the first connection will block on DNS resolution the second connection might time out? Both should work.

from usockets.