Socket SEND()

[Kenneth Brody]

Quoting Fairlight (Mon, 10 Nov 2008 16:23:13 -0500):
[...]
>> > Perhaps you should sit down, take a stress pill, and rethink closing
>> > the socket?"
>> >
>> > NO, CLOSE THE BLOODY SOCKET AS INSTRUCTED!  :) :) :) :) :)
>>
>> Perhaps you need a stress pill as well?  :-)
>
> What, nobody catches 2001 HAL references anymore?  I'm sad!

Well, the quote would be:

     I honestly think you ought to sit down calmly, take a stress pill,
     and think things over.

:-)

> And I actually take four stress pills a day, thanks.
>
>> (And how come you have no nose?)
>
> I stuck it where it didn't belong one too many times.  Someone bit it off.

;-)

[...]
>> The problem that Nancy is running into is trying to continue reading
>> from the socket after all data has been read and the socket has been
>> closed.  (Sort of like reading beyond EOF on a file, except that on a
>> socket, it's an error.)
>
> Do you support MSG_PEEK?  If so, one could use that to check for incoming
> data for number_of_attemts * interval_seconds.  If data shows up, it can be
> read with a subsequent "real" recv().  If not, and the timespan allotted is
> exceeded, one can take the appropriate steps.

I'd have to check, but I don't think that's supported in filePro processing.

-- 
KenBrody at BestWeb dot net        spamtrap: <g8ymh8uf001 at sneakemail.com>
http://www.hvcomputer.com
http://www.fileProPlus.com