I've run into a situation that I'm trying to solve for Windows. It
involves communication between the UI and the exec. I have got to a
point where the UI is trying to UxSend to the open socket and the
exec is trying to WriteSFILE to the same socket. UxSend is set up to
do a select() first to see if the socket is available, but since
WriteSFILE is flooding the socket--it isn't. UxSend then errors out
and exits out hard. So anybody got a solution? If I use
DXMessageOnSocket to check it, it says there is data still on it--but
then how should I go about processing it? UxSend doesn't have access
to the PacketIF construct in order to force it to continue processing
input.
Greg, Martin? Any ideas?
David
--
.............................................................................
David L. Thompson Visualization and Imagery Solutions, Inc.
mailto:[EMAIL PROTECTED] 5515 Skyway Drive, Missoula, MT 59804
Phone : (406)756-7472
