From: bert hubert <ahu@ds9a.nl>
To: Lennert Buytenhek <buytenh@gnu.org>
Cc: netdev@oss.sgi.com
Subject: Re: [PATCH,RFC] explicit connection confirmation
Date: Thu, 7 Nov 2002 17:24:24 +0100 [thread overview]
Message-ID: <20021107162424.GA31447@outpost.ds9a.nl> (raw)
In-Reply-To: <20021107143002.GA23858@gnu.org>
On Thu, Nov 07, 2002 at 09:30:02AM -0500, Lennert Buytenhek wrote:
> > I like having this ability - I dislike offering it to an unsuspecting
> > userspace.
>
> Userspace needs to turn on the option first, so your 'unsuspecting'
> does not apply.
Ah ok, I thought 'TCP_CONFIRM_CONNECT' was a TCP connection state like
SYN_RECV.
> Again, if the app decides to turn on TCP_CONFIRM_CONNECT, then it's
> up to the app to deal with it properly. There are very good reasons
> for not turning on TCP_CONFIRM_CONNECT by default, which is why it
> is not on by default, and why grafting a setsockopt onto every daemon
> there is out there is definitely not a good idea.
Exactly. Ok, cool.
Regards,
bert
--
http://www.PowerDNS.com Versatile DNS Software & Services
http://lartc.org Linux Advanced Routing & Traffic Control HOWTO
next prev parent reply other threads:[~2002-11-07 16:24 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-07 9:32 [PATCH,RFC] explicit connection confirmation Lennert Buytenhek
2002-11-07 11:27 ` bert hubert
2002-11-07 12:09 ` Lennert Buytenhek
2002-11-07 13:36 ` jamal
2002-11-07 15:27 ` Lennert Buytenhek
2002-11-08 11:22 ` jamal
2002-11-08 11:52 ` bert hubert
2002-11-08 11:56 ` Marc Boucher
2002-11-08 18:28 ` Lennert Buytenhek
2002-11-07 13:49 ` bert hubert
2002-11-07 14:30 ` Lennert Buytenhek
2002-11-07 16:24 ` bert hubert [this message]
2003-08-14 13:11 ` Lennert Buytenhek
2003-08-25 11:09 ` Harald Welte
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=20021107162424.GA31447@outpost.ds9a.nl \
--to=ahu@ds9a.nl \
--cc=buytenh@gnu.org \
--cc=netdev@oss.sgi.com \
/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;
as well as URLs for NNTP newsgroup(s).