VB6 Developers Bot v1.0

[MyndFyre]

It has a timer checking every 300 milliseconds if it's connected

You'll never know if it's disconnected if you never send data.  That's why many protocols have things like SID_NULL (keepalive packets) to ensure that a connection doesn't just last forever.

Just out of curiosity, can sending Battle.net the SID_NULL packet, lets say every 15 seconds, be at all dangerous?

Not generally, but IIRC it does count against you on the flood meter.

[Kp]

It has a timer checking every 300 milliseconds if it's connected

You'll never know if it's disconnected if you never send data.  That's why many protocols have things like SID_NULL (keepalive packets) to ensure that a connection doesn't just last forever.

Not entirely true.  If you've enabled the TCP_KEEPALIVE option on the socket, you never need to (explicitly) send data.  The protocol stack will do it for you.  That said, it's not particularly aggressive about doing so, so I wouldn't rely on that behavior for anything more pruning connections on a low traffic network.

[FrOzeN]

It has a timer checking every 300 milliseconds if it's connected

Use the gift given to you through Winsock_Close =p

I am not using the Winsock control, I'm using the API. I have to create the Winsock_Close by capturing in returned events via hooking.

It has a timer checking every 300 milliseconds if it's connected

You'll never know if it's disconnected if you never send data.  That's why many protocols have things like SID_NULL (keepalive packets) to ensure that a connection doesn't just last forever.

Sorry, ment to say ".. if data has arrived." The IsConnected() function just determines if the socket has been closed or not.