TCP/IP concept problem

I have to develop an aplication using client-server model via tcp/ip. The
client is a windows box and the server is a QNX4.25 box. I follow the
example for the server side, placed on QNX TCP/IP Programer´s Guide book, I
did the client part on VB.Net on windows side.

Basically, the client side sends a set of ascii characters to the server
side to comunicate “something”. Once the server has the message (set of
characters) has to reply to the client side confirming everything is ok or
is not ok, sending back a couple of characters.

I am using a stream connection and the aplication works ok in the very basic
way, I mean, sending the characters from the client side to the server side
is ok, the problem arises when the server has to confirm to the client that
message is ok or is not ok. I have not found how to do it.
I am using accept() to wait for a pending connection request and read() to
read the message contens. I am trying to use the write() instruction to
reply but something is missing and can not find what it is. Is the first
time I do something regardind tcp/ip and feel I have not fully understand
the whole picture of it.
I apreciate any kind of advice regardind this.

Thanks.

Oscar E. Soto Hinojosa

Control Adaptable SA de CV

Tel:+ 52 (81) 8399-0180
Fax:+ 52 (81) 8399-0162
Cel: +52 (81) 8396-6327

Oscar E. Soto <osoto@att.net.mx> wrote:

I am using a stream connection and the aplication works ok in the very basic
way, I mean, sending the characters from the client side to the server side
is ok, the problem arises when the server has to confirm to the client that
message is ok or is not ok. I have not found how to do it.
I am using accept() to wait for a pending connection request and read() to
read the message contens. I am trying to use the write() instruction to
reply but something is missing and can not find what it is.

write() would be the correct way to send the reply. Other side would
get it with a read().

Generally, QNX’s TCP/IP programming model is quite standard – any
good Unix/Sockets book will be quite applicable.

e.g. Unix Network Programming by W. Richard Stevens.

-David

Please follow-up to newsgroup, rather than personal email.
David Gibbs
QNX Training Services
dagibbs@qnx.com