Tweet
I am officially going insane over this! 
I have downloaded every example I can find regarding implementing
a TCP server. I was successful in applying Don Dickinson's rserver
solution to my database program, however when I tried calling
database functions in a loop (e.g. appending 100's of records) the
server came to a standstill. A process that would take a second or
two in standalone mode now took 20 or 30 seconds - ouch!
I figure it is a bottleneck with the sending and receiving of
TCP commands so I am trying to put each connection into its
own thread. I have banged my head against the wall so many times
that I can not focus any longer! Everytime the client connects
it GPF's at the call to the create thread.
Can some TCP client/server geniuses please share some code with
me on a simple client/server implementation that uses threads
for each connection????? Maybe I am just missing the boat with
this. If I can get this bottleneck resolved then I am off to the
races because my database DLL has already been modified to handle
both standalone (client only) and multiuser (client/server).
I have code available if anyone is willing to (or brave enough) to
peek into my demented attempt at TCP multithreading
Thanks,
------------------
Paul Squires
mailto:[email protected][email protected]</A>
I have downloaded every example I can find regarding implementing
a TCP server. I was successful in applying Don Dickinson's rserver
solution to my database program, however when I tried calling
database functions in a loop (e.g. appending 100's of records) the
server came to a standstill. A process that would take a second or
two in standalone mode now took 20 or 30 seconds - ouch!
I figure it is a bottleneck with the sending and receiving of
TCP commands so I am trying to put each connection into its
own thread. I have banged my head against the wall so many times
that I can not focus any longer! Everytime the client connects
it GPF's at the call to the create thread.
Can some TCP client/server geniuses please share some code with
me on a simple client/server implementation that uses threads
for each connection????? Maybe I am just missing the boat with
this. If I can get this bottleneck resolved then I am off to the
races because my database DLL has already been modified to handle
both standalone (client only) and multiuser (client/server).
I have code available if anyone is willing to (or brave enough) to
peek into my demented attempt at TCP multithreading
Thanks,
------------------
Paul Squires
mailto:[email protected][email protected]</A>
Comment