SendAsync(msg).Wait(1000) always "false" on custom server

[xarthurx]

I'm buiding a communication between c# (WatsonWebsocket) and cpp (Websocket server).

When calling SendAsync(msg).Wait(1000), it seems the result is always false though I can guarantee the server has received the message.

As I'm not using WatsonWebsocket to build the server, I assume I need to send something back from my custom server so that the WastonClient knows the message is sent correctly?
What should I send back?

#27

[xarthurx]

If I try to use SendAsync(msg).Result it takes forever to return the bool result... Never get it.

[jchristn]

You shouldn't have to send anything back from the server. What happens if you do it without .Wait(1000)?

[xarthurx]

It can send data to the server.
But if the server is not started, the program hangs forever.

Besides, I need sth like this:

[jchristn]

You could always do bool success = _Client.SendAsync(curText); followed by if (!success)

[xarthurx]

You could always do bool success = _Client.SendAsync(curText); followed by if (!success)

I cannot. Otherwise I would not start this issue.

[xarthurx]

check this:

https://stackoverflow.com/questions/45138268/how-to-get-bool-result-from-async-taskbool-function-in-c-sharp-error-cannot

[xarthurx]

I think we're also missing functions like client.IsRunning to check the status of the client?
May I ask how should I check if a client is connected to to server?

[xarthurx]

OK, I got it to work by
bool success = await _Client.SendAsync(curText);
And found Connected properties.

[jchristn]

Right, sorry, I should have said bool success = await ..., good catch!

[xarthurx]

@jchristn when using the client.Start() to start the client, and the the server is at the same time closed, it takes quite long (several seconds) to finish the command.
Would it be possible to expose the waiting time as a parameter?

[xarthurx]

Oh, there is the StartWithTimeout()....

Sorry for bothering. Your naming convention is not similar to the other c# libraries...

[jchristn]

Yeah, some of the naming is inconsistent, but changing it would be breaking. If you want to submit a PR with a cleanup on those items I'd be happy to take it and increment the major version!