I am interested in writing a "server" function on an OpenVMS (ver 7.1) system that will use tcp/ip over ethernet (ucx on OpenVMS) to communicate with a "client" function on a Win2000 based pc.
Basically, server function will use sockets, initialize and wait for/service data requests from client (message formats defined) and then service them.
What I need help on is "What is the appropriate general logic to closing the socket (currently doing SELECT, ACCEPT and RECV, processing the info then closing the socket)? Seems that I am missing some messages when I go back to the next SELECT. Should I / can I do multiple RECV's to see if another message came in while processing last request?
Thanks for any help.
Frazz
Basically, server function will use sockets, initialize and wait for/service data requests from client (message formats defined) and then service them.
What I need help on is "What is the appropriate general logic to closing the socket (currently doing SELECT, ACCEPT and RECV, processing the info then closing the socket)? Seems that I am missing some messages when I go back to the next SELECT. Should I / can I do multiple RECV's to see if another message came in while processing last request?
Thanks for any help.
Frazz