From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Lars Magne Ingebrigtsen Newsgroups: gmane.emacs.devel Subject: Re: Asynchronous DNS Date: Sun, 24 Jan 2016 14:56:30 +0100 Message-ID: References: NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1453643842 13064 80.91.229.3 (24 Jan 2016 13:57:22 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sun, 24 Jan 2016 13:57:22 +0000 (UTC) Cc: emacs-devel@gnu.org To: Stefan Monnier Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sun Jan 24 14:57:12 2016 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1aNLAG-0002Hl-Ga for ged-emacs-devel@m.gmane.org; Sun, 24 Jan 2016 14:57:12 +0100 Original-Received: from localhost ([::1]:60559 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aNLAC-00028r-Ob for ged-emacs-devel@m.gmane.org; Sun, 24 Jan 2016 08:57:08 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:36782) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aNLA0-00028X-6U for emacs-devel@gnu.org; Sun, 24 Jan 2016 08:56:56 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1aNL9w-0000sq-Qn for emacs-devel@gnu.org; Sun, 24 Jan 2016 08:56:56 -0500 Original-Received: from hermes.netfonds.no ([80.91.224.195]:39080) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aNL9w-0000sk-K0 for emacs-devel@gnu.org; Sun, 24 Jan 2016 08:56:52 -0500 Original-Received: from cm-84.215.1.64.getinternet.no ([84.215.1.64] helo=stories) by hermes.netfonds.no with esmtpsa (TLS1.0:DHE_RSA_AES_128_CBC_SHA1:16) (Exim 4.72) (envelope-from ) id 1aNL9a-0002Pj-Ph; Sun, 24 Jan 2016 14:56:30 +0100 Face: iVBORw0KGgoAAAANSUhEUgAAADAAAAAwBAMAAAClLOS0AAAAElBMVEVEQkI9OjuQjYswLi9R Tk5LSEiKlwpbAAACQ0lEQVQ4jcVUQW4bMQwkY/FOVd67HaP3qJsHaFPpThXi/7/S4aYJCrQ9lzAM e8nhDIe06fkfQf818dg/4mXfy+eXV3qQ5kI5U/52uz3vOedSiduie+8+upDR6/f9eJmkm22TEj0m XzRfziZlz6WUHHGlx5JhLm2b0wNH2kTkRGTSmnMNTKl4q3utBQg2Ztqygp4zVSIyM0GCSJQLMwii tNSa68nBGdVnVAYMkcU3JPrmJtOMWCWDXV2ZCIkcGnMJfMlKfMnEpEi4bUw9cfLl5q3PUO8LCCjN UX9R5rAmJgzEFDVKaoL6o6clHh71GHCyFghS3lB7yXlmPhGKhzmU8iTeKDk8WT/oPowm9OlMzciU TcSpPdHDVENsVchX2EC0wZMnujtI1W0tMK4hY6zR3PppSehTlcib0GByhu3u3pd1lPf3WB2oN3Bg cBtA2MADxFAn+RKW0BUP0jb6ZwAMuT318dkHp4GXDXg1obA1dCE6MW2gaADxW/GvLmO0EXKrGMaQ hSXJSJCLK5FEtxYU/ewyPkAnuTXstZ+TuwiTJGmTcKJYQFruJ1PqMUgDSwL5Blv78JUWaHCK0w4D x6MRB6Uda2sHmL35gEl0+xCJuXy0LsvT8JhjLc+mCauyjSTo6XB5R7QOA4P7OiTUpRSIQxsL7qDg 6nMsmU0n9vG1H312T61DV+vdBPvAhzgGwa75BVeD5StjmSy49vtoqQkOhDdubV0FDPh5RavYJWQe NnAd01kNRBiw7DXvf8Qr9f7213+Gn+FVuevRe/ubAAAAAElFTkSuQmCC In-Reply-To: (Stefan Monnier's message of "Sat, 23 Jan 2016 23:49:12 -0500") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/25.1.50 (gnu/linux) X-MailScanner-ID: 1aNL9a-0002Pj-Ph MailScanner-NULL-Check: 1454248590.9117@yfVSnQzdDsoOtWrj2EifNA X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 80.91.224.195 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:198693 Archived-At: Stefan Monnier writes: >> (resolve-name "foo.bar" >> (lambda (status ip) >> (make-network-process :host "foo.bar" :ip ip ...))) > > If possible, I'd rather the async-dns-resolution be done directly as > part of make-network-process. If we go for a C-level solution here, then that would definitely be preferable. `make-network-process' would then take an :async parameter and return as soon as it's started name resolution, returning a process object in a new "resolving" state. The connection would be completed from the DNS callback, or from the event loop, possibly. Error handling would be somewhat different in :async, of course. -- (domestic pets only, the antidote for overdose, milk.) bloggy blog: http://lars.ingebrigtsen.no