🚀 go-pugleaf

"Remy Lebeau \(TeamB\)" <no.spam@no.spam.com> wrote:
>
>"Ulrik Nilsson" <di2niul@chl.chalmers.se> wrote in message
>news:413d624f$1@newsgroups.borland.com...
>
>> As you guessed that didn't help me. Maybe I should have told
>> you in the first place but I still get the "Terminate Thread Timeout"
>> from the server application.
>
>You never said anything about getting that error before.  The only way that
>error can occur is if the peer threads are not terminating in a timely
>fashion.  Given the code you have shown so far, taking into account the
>changes I mentioned earlier, that should never be happening.

Hmmm...


Hi, again!

Well this dosen't look good.

I just can't see whats wrong in my application so,

if you have got the time (or a friend of yours),

could you write the client and server code on your machine and then post it here?

The specification is very simple.

Client:

Make a connetion to a server via a button click.

Close the connection to the server via a button click.

Close the application and the tcp-connection via a button click.

Send a text (command) to the server and recieve a text via a button click.

A information if the client are connected to the server or not.

Server:

Start the server via a button click.

Close the connections to all clients via a button click.

Close the application and all tcp-connections via a button click.

Answer the specified command that the client sent and reply.

A counter that tells how many current connections there is via a label.


Indy version: Indy_9_00_14

Components: TCPCLient and TCPServer
 
Language: C++


If I have missed something, post a reply and ask.


Regards Ulrik