Jump to content
mitzi

wsConnected triggered even if client not connected

Recommended Posts

hm, i'm trying, but despite the fact I have┬áBUILTIN_TIMEOUT defined, property┬áTimeoutConnect has no effect ­čś×

What is scale? Seconds or milliseconds?

Share this post


Link to post
On 1/10/2020 at 5:45 PM, mitzi said:

hm, i'm trying, but despite the fact I have┬áBUILTIN_TIMEOUT defined, property┬áTimeoutConnect has no effect ­čś×

What is scale? Seconds or milliseconds?

If you define timeout, you'll have OnTimeout event triggered, that's all. You'll have to add an action (i.e. close the socket) by yourself

Share this post


Link to post

Thanks, that's it. And timeout is defined in seconds or milliseconds?

Share this post


Link to post

Of course I did. But when i set TimeoutConnect either to 5 or 5000 OnTimeout event was triggered after 3-4 seconds after Connect was called regardless of TimeoutConnect value. So I'm a little confused.

Share this post


Link to post

Weird, I have timeouts working OK.

Socket.TimeoutConnect := Settings.ConnTimeout*MSecsPerSec;

Share this post


Link to post

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
├Ś