Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Winsock is busy long time after disconnecting to remote
Message
 
To
28/10/2003 04:32:55
General information
Forum:
Visual FoxPro
Category:
Client/server
Miscellaneous
Thread ID:
00843408
Message ID:
00843906
Views:
43
>Hello everybody,
>
>I have the following program: Winsock is used to connect 2 computers as server and client with TCP protocol. They communicate nicely and promptly.
>The only problem is that when disconnecting one , the other remains busy for a relatively long period: sometimes 20 seconds, but sometimes 4 seconds. I put a timer in the form to "see" changes in Winsock.state, I also set Application.AutoYield to .F. (then to .T.) , but the same result. I know that Windows manages the connection between the 2, but did anyone experience this ? What could I do to decrease that busy time ?
>
>Thank You,
>Mihai .

If you are using the Winsock control, add the Winsock1.Close command to be executed in the CLOSE event.

I had this problem with a client/server project I wrote in FoxPro a few months back.
Brian Seekford
Seekford Solutions, Inc.
http://www.SeekfordSolutions.com
Internet ActiveX Controls and .NET Class Libraries.
SMTP/S FTP POP3/S HTTP/S SNTP MIME PING WHOIS TRACEROUTE NNTP DNS MX
Base64, UUEncode, yEnc, MD5, SHA1, URL, Quoted-Printable.
Resizer and Tooltips
Email Verification and more. Check us out!
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform