Comments by psychokeith (Top 2 by date)

The "Client" target is a Windows 2000 Server with Single Core - Hyperthreading disabled - and the other machine is a fully threaded multi-cored XP machine. However I am developing the app on two XP machines with hperthreading enabled - and I still have the problem that if the client is sending data the Server listens and picks up the changes, but does not send its own data back down the socket for the client to update in a timely fashion

The Port I am referring to is from
Client::Client( const char* host, const char* port, AddStringListener* pDebugWin )
etc
{
m_address = INETAddr( host, port );
}
where port is set at 3040 or there abouts

I hope this clarifies a few things. The actual code contains alot of specific code, so my question is based on generalities, so that I can look at a few solutions. I am currently chopping up the Data so the client signals work as they do now with the Server listening on say 3040, and the old Server signals being seperated out so the Client machine becomes a Listening Server Process and the Server becomes its client sending on say 3041 with the "client" listening as a Server on that port. This probably could get round the "multithreading" as they would then be two distinct applications. I dont know if this will work but it would seem a logical way of improving throughput! However. I am just open to suggestions at present! It might indeed be that the protoclos are not set up correctly, or I might need a stream in one direction and a UDP connection in the other direction. At the moment all data is queued and streamed. Again the bugs may be in the streaming, but it works extemely well in one direction!