From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: Asynchronous DNS Date: Mon, 08 Feb 2016 20:22:26 +0200 Message-ID: <83vb5zoye5.fsf@gnu.org> References: <87si1gx6wz.fsf@gnus.org> <86y4b5zvzt.fsf@gmail.com> <8760y9kwrk.fsf@gnus.org> <8760y7nag7.fsf@gnus.org> <83oabzzsjq.fsf@gnu.org> <87fuxazkfe.fsf@gnus.org> <83io25yeqk.fsf@gnu.org> <87h9hpnreg.fsf@gnus.org> <83y4b0wi7m.fsf@gnu.org> <87si17evk6.fsf@gnus.org> <83twlnvcz2.fsf@gnu.org> <87vb63obm3.fsf@gnus.org> <87r3gqmg6g.fsf@gnus.org> <83egcqtfnm.fsf@gnu.org> <86mvrdmk8p.fsf@realize.ch> <83mvrcsefa.fsf@gnu.org> <871t8o556n.fsf@gnus.org> Reply-To: Eli Zaretskii NNTP-Posting-Host: plane.gmane.org X-Trace: ger.gmane.org 1454955785 18715 80.91.229.3 (8 Feb 2016 18:23:05 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 8 Feb 2016 18:23:05 +0000 (UTC) Cc: a.s@realize.ch, emacs-devel@gnu.org To: Lars Ingebrigtsen Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Feb 08 19:23:05 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 1aSqSm-0005zr-9Y for ged-emacs-devel@m.gmane.org; Mon, 08 Feb 2016 19:23:04 +0100 Original-Received: from localhost ([::1]:47572 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aSqSl-0002vO-PD for ged-emacs-devel@m.gmane.org; Mon, 08 Feb 2016 13:23:03 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:38825) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aSqSV-0002vD-Gz for emacs-devel@gnu.org; Mon, 08 Feb 2016 13:22:51 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1aSqSR-0003TT-G7 for emacs-devel@gnu.org; Mon, 08 Feb 2016 13:22:47 -0500 Original-Received: from fencepost.gnu.org ([2001:4830:134:3::e]:34834) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aSqSR-0003TO-Cs; Mon, 08 Feb 2016 13:22:43 -0500 Original-Received: from 84.94.185.246.cable.012.net.il ([84.94.185.246]:1572 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_128_CBC_SHA1:128) (Exim 4.82) (envelope-from ) id 1aSqSQ-0006i3-J9; Mon, 08 Feb 2016 13:22:43 -0500 In-reply-to: <871t8o556n.fsf@gnus.org> (message from Lars Ingebrigtsen on Mon, 08 Feb 2016 13:03:44 +1100) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 2001:4830:134:3::e 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:199544 Archived-At: > From: Lars Ingebrigtsen > Cc: Alain Schneble , emacs-devel@gnu.org > Date: Mon, 08 Feb 2016 13:03:44 +1100 > > Hm... I don't understand. An application that wants 'immediate will > just say ":nowait 'immediate". The only thing that examines the :nowait > parameter (to distinguish 'immediate, nil and non-nil) is > make-network-process. These two places could be many levels apart. The place where 'immediate' is used and the programmer who uses it might not be aware of all of the implications. E.g., the same set of parameters could be used for several different series of calls to network-related APIs. What I suggest is a way to let applications still work even if they didn't make all the refactoring, or if the place to refactor is out of their control, or whatever.