This is the mail archive of the
cygwin
mailing list for the Cygwin project.
RE: recv and errno during a connection reset/closed by peert
- From: "Peter A. Castro" <doctor at fruitbat dot org>
- To: cygwin at cygwin dot com
- Cc: Peter Stephens <ptfoof at sbcglobal dot net>
- Date: Tue, 29 Mar 2005 17:16:46 -0800 (PST)
- Subject: RE: recv and errno during a connection reset/closed by peert
- References: <!~!UENERkVCMDkAAQACAAAAAAAAAAAAAAAAABgAAAAAAAAAUKQItienSEKG+9226yKd5cKAAAAQAAAAdWX/pT74GUisDog/o7TE3gEAAAAA@sbcglobal.net> <Pine.CYG.4.58.0503291040080.3732@fordpc.vss.fsi.com>
On Tue, 29 Mar 2005, Brian Ford wrote:
On Tue, 29 Mar 2005, Peter Stephens wrote:
I have thought about your suggestion and it makes a lot of sense.
It seems like your suggestion would be very portable. A good suggestion and
the most likely route for me at this point.
Not to me. Maybe I'm missing something, but it seems you are going to a
lot of effort to poorly recreate poll/select?
Why? If you are doing sequential, non multi-plexed, reads why do poll or
select? Sitting in read is more optimal and the read should return
either data or an error. The flaw in recv is that it returns a non-error
non-data status. Perhaps it would be better to switch to using read()
instead of recv?
This is really getting off-topic, though.
Yes. Isn't it fun ?-)
--
Brian Ford
--
Peter A. Castro <doctor@fruitbat.org> or <Peter.Castro@oracle.com>
"Cats are just autistic Dogs" -- Dr. Tony Attwood
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/