U++ forum: Welcome to the forum

Re: Problem with websocket connect method [message #49011 is a reply to message #49010]

Fri, 24 November 2017 23:05

Oblivion
Messages: 1093
Registered: August 2007

Senior Contributor

Quote:

Yes. I'm using AsyncWebSocket example. All changes I've done was removing ClientEmulation from async server and replacing listening port from 12321 to 8888. Unfortunately, the problem wasn't solved

Ah, in the meantime I got what is wrong with your code.

Let me try to briefly explain the problem (as far as I can see):

Before you can send or receive anything to the server, the client needs to be connected to the server, and that is generally done after a "handshake"
You see, your "non-blocking" code is simply interrupting that handshake phase, hence the connection is forced to be closed.
You are trying to send and receive data in the middle of connection process.

But the real problem I see is there is no way (at least not that I can find one) to know if the connection (handshake) is successful, and the client is ready. E.g. In similar scenarios, I personally use a Do() method which returns a boolean value so that I can detect the "end" of any operation (be it successful or erroneous). But WebSocket::Do() doesn't return anything, so we can't know if the Connect() operation is finished (except on failures).

This is probably by design and Mirek can probably give you a better explanation.

I'm sorry that I cannot be very helpful this time.

Best regards,
Oblivion

Github page: https://github.com/ismail-yilmaz
upp-components: https://github.com/ismail-yilmaz/upp-components
Bobcat the terminal emulator: https://github.com/ismail-yilmaz/Bobcat

[Updated on: Sat, 25 November 2017 09:52]

Report message to a moderator