[En-Nut-Discussion] NutTcpAccept Timeout
ralph.mason at telogis.com
Tue Jun 24 20:47:54 CEST 2003
For dynamic connections - eg a FTP server, you expect a client to connect,
but if it doesn't do it in a given time you timeout.
I changed my implementation to look like
NutTcpAccept(SOCKET* s,u_long timeout_ms)
It seems to work fine, and as I Close the socket right after it doesn't
matter if a client manages to connect after the accept has returned.
> -----Original Message-----
> From: en-nut-discussion-admin at egnite.de
> [mailto:en-nut-discussion-admin at egnite.de]On Behalf Of Harald Kipp
> Sent: Wednesday, 25 June 2003 12:52
> To: en-nut-discussion at egnite.de
> Subject: Re: [En-Nut-Discussion] NutTcpAccept Timeout
> I can imagine situations, where timeouts are required
> for connect, send and receive. But I have no idea,
> why someone may need an accept timeout. It looks to
> me like polling for clients. Can you please explain?
> En-Nut-Discussion mailing list
> En-Nut-Discussion at egnite.de
> Incoming mail is certified Virus Free.
> Checked by AVG anti-virus system (http://www.grisoft.com).
> Version: 6.0.491 / Virus Database: 290 - Release Date: 18/06/2003
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.491 / Virus Database: 290 - Release Date: 18/06/2003
More information about the En-Nut-Discussion