From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Bernard Blackham <bernard@blackham.com.au>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Werner Almesberger <werner@almesberger.net>
Subject: Re: Non-blocking sockets, connect(), and socket states
Date: Sun, 01 May 2005 14:46:04 +0100 [thread overview]
Message-ID: <1114955160.11309.160.camel@localhost.localdomain> (raw)
In-Reply-To: <20050428103451.GG4798@blackham.com.au>
On Iau, 2005-04-28 at 11:34, Bernard Blackham wrote:
> Should it be the kernel's responsibility to set SS_CONNECTED when
> the connection is established? Or should I go file bugs and submit
> patches on all the applications that use non-blocking sockets and
> don't call connect() a second time?
See posix 1003.1g drafts. I believe from the state diagram there that
you should call connect() again once it completes.
prev parent reply other threads:[~2005-05-01 13:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-28 10:34 Non-blocking sockets, connect(), and socket states Bernard Blackham
2005-05-01 13:46 ` Alan Cox [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1114955160.11309.160.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=bernard@blackham.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=werner@almesberger.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox