× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  1.  Home
  2. MI400
  3. April 2002

Re: what is a reasonable socket select() wait time?(Gene_Gaunt@xxxxxxxxxxxxxxx)

Try looking at the setsockopt() call with TCP_NODELAY.  It means deliver the
data immediately, and don't wait to fill buffers.  E.g.

setsockopt(iSocket, IPPROTO_TCP, TCP_NODELAY, on, sizeof(on))

> Sometimes select() fails to detect when more data is truly available.  I'm
> not sure why select() fails.  My client receive buffer size is huge; I know
> the server never completely fills it.  I know the client sets the fd_set
> bits correctly.

> Why does the select() periodically fail?  How can my client truly, TRULY
> determine if more data is available from the server?  Do I need a non-zero
> wait time?  What is a reasonable value?

--
Jeffrey Stevens (jssteven@us.ibm.com)
TCP/IP Applications & iSeries Connect
T/L: 852-5488   Fax: 852-5421

As an Amazon Associate we earn from qualifying purchases.

This thread ...
Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 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.