Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations derfloh on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

CLIENT/SERVER TCP BLUES

Status
Not open for further replies.

TrueCode

MIS
Joined
Sep 30, 2003
Messages
71
Location
LC
I have a client connecting to a server,the server creates a dynamic answering socket which ACCEPT()s the connection request. The connection state at both end is 7 (connected). The client then sends a message [this.name='client1'] to the server on that same socket. The server receives it and performs a macro substitution on it, thus renaming that socket which was just created on the server side to 'client1'

In the dataarrival code on the server side, the server sends a message back to client whenever that message had the effect of changing the sockets name. So, immediately after the server processed the first message coming from the client (this.name='client1'), in the same dataarival method, does a .senddata('lconnected = .t.') to the client.

For some strange reason, the client keeps that message 'lconnected = .t.' , and only processes it in its dataarrival method, when a subsequent message comes through. And when that subsequent message comes, its .getdata buffer ends up with the two messages.




------------------------------------->

"I have sought your assistance on this matter because I have exhausted all the help that I can find. You are free to direct me to other source of help"
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top