🚀 go-pugleaf

"mat" <mat@hotmail.com> wrote in message
news:45cbd7c8$1@newsgroups.borland.com...

> hello,im using a socketconnection component

Which component specifically?

> the code is in a separate thread and i have some
application->processmessages
> in order to get some visual feedback (e.g. a messagebox before
> it starts connected and a messagebox if it connects).

You should not be calling Application->ProcessMessages() in a worker
thread.  Only call it in the main thread.  Besides, you don't need it
anyway.  You can call the Win32 API MessageBox() directly in a worker
thread without processing any messages at all, as it has its own
message processing internally.

> if its not up (e.g. if im not running the scktsrv.exe)it throws an
exception.

As it should be.

> when i try to connect to an not existing pc (wrong ip) the system
> freezes and waits for a rather big timeout.

Again, as it should be.  If the IP cannot be reached immediately, it
can take a long time for the OS to figure out whether the IP is
actually valid or not.

> if i try to connect to a firewalled pc (which blocks such incomming)
> it freezes again and waits for a rather big timeout again.

See above.  If the firewall is blocking communications, then it is
likely also blocking the packets that the OS needs to determine
whether the machine is present or not at the IP.

> is this something i can fix?

The only thing you can do is implement your own timeout on the
connection manually.  You did not say whether the socket was
asynchronous or synchronous.  It makes a big difference in how to
implement such a timeout.

> the waiting timeout is very big

Such is the nature of sockets, especially on Windows.  Microsoft likes
to use large timeouts that cannot be changed.

> the program freezes (although its in its own thread).

The program cannot be freezing unless you are making your main thread
wait on the socket thread while it is waiting on the socket.


Gambit