Good News Everybody!
The new search engine is LIVE!
Please report any problems to david (at) midrange.com.
|
> I had always assumed (and you know what happens when we assume...) that > the part of code that check for disconnected clients was the line that > checked excpset, but you are saying that it is the return of > (ReadClient(C) < 0) when we know that there is data in the buffer? Correct. I don't know why I'm checking the exception set at all... Possibly because out-of-band data used to cause memory corruption in Win95, so I got in the habit of always terminating the program when I received it to prevent further corruption. That was fixed in Win95, and in any case has nothing to do with OS/400... I don't know. > Knowing that I had never sent OOB data in the handheld application, > should I even bother checking excpset? My only _guess_ as to why I am > getting OOB data is because it is M$ .Net is doing it for me somewhere > under the covers? Yeah, like I said before, I think it's probably doing it to verify the connection is operating properly. If I were you, I'd set SO_OOBINLINE with setsockopt() (so that out of band data doesn't sit in a buffer indefinitely wasting resources) and then ignore the exception set, just check read set... Good Luck
This mailing list archive is Copyright 1997-2026 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.