I need to write to a socket and receive data from that socket.
Has anyone out there been successful with this?
I tried to telnet a socket address and was successful. However, using the FWH sample socket prg's I receive a -1 on that same ip / port address.
Any magic required here?
sockets
- don lowenstein
- Posts: 196
- Joined: Mon Oct 17, 2005 9:09 pm
- Contact:
sockets
Don Lowenstein
www.laapc.com
www.laapc.com
- Antonio Linares
- Site Admin
- Posts: 37481
- Joined: Thu Oct 06, 2005 5:47 pm
- Location: Spain
- Contact:
- don lowenstein
- Posts: 196
- Joined: Mon Oct 17, 2005 9:09 pm
- Contact:
Antonio,
I'm having erratic results on reading the return response from the host. I have inserted timing loops, etc but can't get consistant.
With the test programs and msgstop's and debugger, things work well. In my application, it's almost like sometimes I'm active and receive the host messages, other times I "miss" them. I'm telling my app to sleep() and inkey(.25) etc, then testing for the getdata(), but most times (not all) the returned data is empty. I do know that the host side is returning data.
Question: Why won't the getdata() method work consistantly? Also, in the sample programs, when the socket is getting ready to close, a msginfo() is invoked, and this in turn invokes the onread event. Almost like without the msginfo() the socket doesn't "wake up" for handling the read event. Does this make sense?
How can I control the onread event BEFORE ending the socket.
I'm having erratic results on reading the return response from the host. I have inserted timing loops, etc but can't get consistant.
With the test programs and msgstop's and debugger, things work well. In my application, it's almost like sometimes I'm active and receive the host messages, other times I "miss" them. I'm telling my app to sleep() and inkey(.25) etc, then testing for the getdata(), but most times (not all) the returned data is empty. I do know that the host side is returning data.
Question: Why won't the getdata() method work consistantly? Also, in the sample programs, when the socket is getting ready to close, a msginfo() is invoked, and this in turn invokes the onread event. Almost like without the msginfo() the socket doesn't "wake up" for handling the read event. Does this make sense?
How can I control the onread event BEFORE ending the socket.
Don Lowenstein
www.laapc.com
www.laapc.com
- James Bott
- Posts: 4654
- Joined: Fri Nov 18, 2005 4:52 pm
- Location: San Diego, California, USA
- Contact: