From: erik quanstrom <quanstro@quanstro.net>
To: arisawa@ar.aichi-u.ac.jp, 9fans@9fans.net
Subject: Re: [9fans] bug in authdial()
Date: Sat, 21 May 2016 10:04:01 -0700 [thread overview]
Message-ID: <ee8d9c4e298eb81f8ea27ce180754902@lilly.quanstro.net> (raw)
In-Reply-To: <9154AB0B-6527-4B44-ABEA-6CADEC4AF038@ar.aichi-u.ac.jp>
On Fri May 20 21:48:40 PDT 2016, arisawa@ar.aichi-u.ac.jp wrote:
> parallel dialing would be fine.
> I guess both cinap and erik have examined labs code.
> any problem with it?
i don't use this code.
i think the problem with parallel dial is that like the tricks we used to play in
nsec()—it assumes things about the calling environment. for starters, it's going
to break anything that's already forking as it may eat wait messages.
it's been a while since i looked at this, but i think parallel dialing requires a
bit more of a rethink of the dialing code than just hacking in a fork. without
restructuring the system, i think one would be forced into a dial device so that
any forking/threading could escape the current running environment.
the original problem this code was trying to solve was the fact that many connections
can't do ip6, and dialing ip6 slows down the connection quite a bit.
this problem is a little easier to fix. cs needs to do a little more work to filter out
impossible connection types. for example, if one's internet connection is not ip6
capable, then cs should be instructed to not return ip6 addresses.
- erik
next prev parent reply other threads:[~2016-05-21 17:04 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-18 0:43 arisawa
2016-05-18 9:14 ` cinap_lenrek
2016-05-19 14:45 ` arisawa
2016-05-19 15:43 ` lucio
2016-05-19 15:48 ` Charles Forsyth
2016-05-20 4:58 ` arisawa
2016-05-20 22:04 ` Skip Tavakkolian
2016-05-20 22:25 ` Charles Forsyth
2016-05-21 4:46 ` arisawa
2016-05-21 17:04 ` erik quanstrom [this message]
2016-05-21 23:11 ` Lyndon Nerenberg
2016-05-21 23:16 ` erik quanstrom
2016-05-21 17:06 ` erik quanstrom
2016-05-21 3:24 ` arisawa
2016-05-23 14:27 ` arisawa
2016-05-20 22:07 ` Skip Tavakkolian
2016-05-21 2:25 ` Skip Tavakkolian
2016-05-21 7:00 ` arisawa
2016-05-21 16:51 ` erik quanstrom
2016-05-21 21:45 ` Skip Tavakkolian
2016-05-21 21:48 ` erik quanstrom
2016-05-21 22:16 ` Skip Tavakkolian
2016-05-21 21:50 ` erik quanstrom
2016-05-21 22:17 ` Skip Tavakkolian
2016-05-21 22:34 ` erik quanstrom
2016-05-21 23:03 ` Skip Tavakkolian
2016-05-21 23:31 ` erik quanstrom
2016-05-21 22:53 ` David du Colombier
2016-05-18 13:06 ` Charles Forsyth
2016-05-18 17:03 ` Skip Tavakkolian
2016-05-19 4:07 ` arisawa
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=ee8d9c4e298eb81f8ea27ce180754902@lilly.quanstro.net \
--to=quanstro@quanstro.net \
--cc=9fans@9fans.net \
--cc=arisawa@ar.aichi-u.ac.jp \
/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).