Board index » delphi » TIdTCPServer.Active question.

TIdTCPServer.Active question.

Finally I am trying to port some of my server application from Winshoe to

Quote
Indy. I wrote:

MyTCPServer.Active := true;

The above statement is simple, but when the port on the host machine has
already been allocated, it won't raise any exception . The Active property
will intact as True, but the server is not actually running.

Any work around? I am using the lastest Indy version (the offical release).

Thanks to the wonderful Indy Team!!!

 

Re:TIdTCPServer.Active question.


That will give an exception in Winshoe if I recall it correctly. I have just
tried it with Indy (8.0.21) and it won't raise any exception, and the Active
property will remain True.

"AkiraBBQ" <akira...@es.co.nz> ???g??l
news:95mpas$vb3@bornews.inprise.com...

Quote
> Finally I am trying to port some of my server application from Winshoe to
> Indy. I wrote:

> MyTCPServer.Active := true;

> The above statement is simple, but when the port on the host machine has
> already been allocated, it won't raise any exception . The Active property
> will intact as True, but the server is not actually running.

> Any work around? I am using the lastest Indy version (the offical
release).

> Thanks to the wonderful Indy Team!!!

Re:TIdTCPServer.Active question.


I did a sample application and yes it goes active but mosty interesting is
that if you run netstat -na you will see that there is two sockets that
listen on the same port. This much more smells like winsock bug ;-))

Doychin
doic...@5group.com

Quote
"AkiraBBQ" <akira...@es.co.nz> wrote in message

news:95mpas$vb3@bornews.inprise.com...
Quote
> Finally I am trying to port some of my server application from Winshoe to
> Indy. I wrote:

> MyTCPServer.Active := true;

> The above statement is simple, but when the port on the host machine has
> already been allocated, it won't raise any exception . The Active property
> will intact as True, but the server is not actually running.

> Any work around? I am using the lastest Indy version (the offical
release).

> Thanks to the wonderful Indy Team!!!

Re:TIdTCPServer.Active question.


At least it doesn't happen to Winshoe, does it?

"Doychin Bondzhev" <doic...@5group.com> ???g??l news:3a7fd2f9_1@dnews...

Quote
> I did a sample application and yes it goes active but mosty interesting is
> that if you run netstat -na you will see that there is two sockets that
> listen on the same port. This much more smells like winsock bug ;-))

> Doychin
> doic...@5group.com

Other Threads