|
We are in the process of writing a new sockets program to talk to a new vendor., The vendor is the server and we are the client. We connect to them OK and then send our information. This is where the problem occurs. They hand off the connection to another socket and they still see us connected to the first socket, so they don't get the information we send. Is there any coding we have to do to handle the new connection? I thought it was done "automagically" but I'm beginning to think not. Heres what we run: Create a socket descriptor for the server process to bind. EVAL SrvrSktId = Socket(AF_INET :SOCK_STREAM :0) ** Set socket descriptor to be reuseable. c EVAL RtnCd = SetSockOpt(SrvrSktId C :SOL_SOCKET C :SOL_REUSEADDR C :%ADDR(On) C :%SIZE(On)) * Connect to the server C Eval RtnCd = Connect(SrvrSktId: C %Addr(ServerAddr) : C %Size(ServerAddr) ) C EVAL svaddrlen = %SIZE(serveraddr) C IF NOT *IN68 C EVAL RtnCd2 = Write(SrvrSktId C :%ADDR(ReceiveDs) C :ReceiveLen) Any help would be greatly appreciated. Ron Hawkins
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.