I'm no expert - but how about doing the connect
(and for that matter subsequent socket calls) in a separate
thread?
if you get bored waiting for the connect to complete
kill the thread.
(all usual disclaimers in effect)
ns
-----Original Message-----
From: Peter Hyde <[EMAIL PROTECTED]>
To: Multiple recipients of list offtopic <[EMAIL PROTECTED]>
Date: Wednesday, 27 September 2000 12:50
Subject: [DUG-OFFTOPIC]: Winsock
Hi y'all,
I wonder, is anybody here sufficiently familiar with Winsock
programming to answer this conundrum?
"I don't know how can I force a winsock API function call like
'connect' to exit before returning success or failure."
It arises from a need we have in TurboNote to allow users to cancel
a note send which clearly isn't working (e.g. the destination
computer isn't present, or they've sent an email to a dial-up SMTP
server and TurboNote can't find its address via a DNS call).
We have an "abort" icon to click, but basically the click isn't
recognised/dealt with until the lower level API call is done with,
which can take quite a while in cases such as those above. Does
anyone have any suggestions about ways in which we can handle
this, perchance?
TIA.
cheers,
peter
============================================
Peter Hyde, WebCentre Ltd & SPIS Ltd, Christchurch, New Zealand
* Web automation for online periodicals: http://TurboPress.com
* TurboNote+: http://TurboPress.com/tbnote.htm
-- easy, small, handy onscreen sticky notes
---------------------------------------------------------------------------
New Zealand Delphi Users group - Offtopic List - [EMAIL PROTECTED]
Website: http://www.delphi.org.nz
---------------------------------------------------------------------------
New Zealand Delphi Users group - Offtopic List - [EMAIL PROTECTED]
Website: http://www.delphi.org.nz
