From: Lars Ingebrigtsen <larsi@gnus.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Paul Eggert <eggert@cs.ucla.edu>, emacs-devel@gnu.org
Subject: Re: Asynchronous DNS resolving
Date: Sat, 14 Feb 2015 14:44:00 +1100 [thread overview]
Message-ID: <87iof5i2db.fsf@building.gnus.org> (raw)
In-Reply-To: <jwv61b57hb1.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Fri, 13 Feb 2015 14:20:59 -0500")
Stefan Monnier <monnier@iro.umontreal.ca> writes:
> Actually, do we really need to make the lookup Elisp-visible? I mean,
> don't we currently just pass the DNS name to make-network-process which
> then does the DNS lookup and the TCP connect? If so, we don't really
> need to make getaddrinfo_a visible at the Elisp level, we just
> need to make use of it in make-network-process if :nowait was specified.
>
> Am I missing something?
No, I think that's a great idea. Making `make-network-process' totally
asynchronous would be good for general asynchronousness (that should be
a word), too, since the handshake part is synchronous today, I think.
*looks at documentation* Oh, right. There's :nowait, so it would make
sense to only use getaddrinfo_a if we've got a :nowait connection.
I can take a look at implementing this (if nobody else feels inspired
to), but I've got one questions to start with:
Is getaddrinfo_a available on all the platforms we care about? Or is
there a gnulib module for compatibility or something?
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog http://lars.ingebrigtsen.no/
next prev parent reply other threads:[~2015-02-14 3:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-13 7:10 Asynchronous DNS resolving Lars Ingebrigtsen
2015-02-13 7:21 ` Paul Eggert
2015-02-13 7:32 ` Lars Ingebrigtsen
2015-02-13 7:58 ` Paul Eggert
2015-02-13 19:20 ` Stefan Monnier
2015-02-14 0:06 ` chad
2015-02-14 3:44 ` Lars Ingebrigtsen [this message]
2015-02-14 6:20 ` Paul Eggert
2015-02-15 4:54 ` Lars Ingebrigtsen
2015-02-13 8:46 ` Eli Zaretskii
2015-02-13 9:02 ` Lars Ingebrigtsen
2015-02-15 5:31 ` Lars Ingebrigtsen
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=87iof5i2db.fsf@building.gnus.org \
--to=larsi@gnus.org \
--cc=eggert@cs.ucla.edu \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.