From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Juanma Barranquero Newsgroups: gmane.emacs.devel Subject: Re: [PATCH] GnuTLS support on Woe32 Date: Tue, 3 May 2011 01:05:30 +0200 Message-ID: References: <87ipvwl1nx.wl%claudio.bley@gmail.com> <87ipuubao6.fsf@lifelogs.com> <87fwpjfkkz.fsf@lifelogs.com> <87bp072fb1.fsf@lifelogs.com> <874o5vimm5.fsf@lifelogs.com> <87zknjmcyk.fsf@lifelogs.com> <87sjta2zvp.fsf@lifelogs.com> <87liyzglkh.fsf@lifelogs.com> <4DB77682.1070605@gmail.com> <8762q04ba1.fsf@lifelogs.com> <87hb9dufao.fsf@lifelogs.com> <87oc3kudag.fsf@lifelogs.com> <87zkn4sx43.fsf@lifelogs.com> <87aaf4ajmz.fsf@stupidchicken.com> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Trace: dough.gmane.org 1304377580 7582 80.91.229.12 (2 May 2011 23:06:20 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Mon, 2 May 2011 23:06:20 +0000 (UTC) Cc: Ted Zlatanov , emacs-devel@gnu.org To: Chong Yidong Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue May 03 01:06:16 2011 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([140.186.70.17]) by lo.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1QH2C0-0004AC-AN for ged-emacs-devel@m.gmane.org; Tue, 03 May 2011 01:06:16 +0200 Original-Received: from localhost ([::1]:54394 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QH2Bz-0007Em-HV for ged-emacs-devel@m.gmane.org; Mon, 02 May 2011 19:06:15 -0400 Original-Received: from eggs.gnu.org ([140.186.70.92]:51659) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QH2Bw-0007Eh-Aj for emacs-devel@gnu.org; Mon, 02 May 2011 19:06:13 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1QH2Bv-0006GZ-7h for emacs-devel@gnu.org; Mon, 02 May 2011 19:06:12 -0400 Original-Received: from mail-gx0-f169.google.com ([209.85.161.169]:47018) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QH2Bu-0006GV-Ps for emacs-devel@gnu.org; Mon, 02 May 2011 19:06:11 -0400 Original-Received: by gxk23 with SMTP id 23so2630411gxk.0 for ; Mon, 02 May 2011 16:06:10 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type:content-transfer-encoding; bh=JCDzFYIerkHu0IemcjBRRNM0Nxh3sgFyN8sMbdTQBCg=; b=grkuOGZXg2rar0sJr/XU0fil8k/Hs3i4ZVI6OcVe5YwF3uZQYOIlDtWSjo2DbIUy9D UWQpE+e+iG12sqsNYwMZz9+ny+ch2w0CT+SnUfDO+PQmYoS9JqQnAsdJ4ZoJUVyOb7G8 TVay2oNJB04MqEErwSVLxkNHsZ5A/z5EPBGiY= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:content-transfer-encoding; b=MaUpG2pk7fFSg0gA0Hl/6m6M+gaaQQ77R/j3YZZn1LhTb3ktY4obh6IAE9c/4Xj4n7 HVGVIE7RIqvZo2Z2evJnbmjJjl3CWTIYG+mkfASVzRpUHiNStP5s+FybqzWhEMdc+YsN 2I+pSFcn9RFs+qn2g2WEHCey58KMGhbd0X6tQ= Original-Received: by 10.236.182.162 with SMTP id o22mr2406895yhm.495.1304377570166; Mon, 02 May 2011 16:06:10 -0700 (PDT) Original-Received: by 10.147.182.5 with HTTP; Mon, 2 May 2011 16:05:30 -0700 (PDT) In-Reply-To: <87aaf4ajmz.fsf@stupidchicken.com> X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6 (newer, 2) X-Received-From: 209.85.161.169 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:139015 Archived-At: On Mon, May 2, 2011 at 23:16, Chong Yidong wrote: > In the case of open-network-stream, why do you need to use > gnutls-available-p? =C2=A0Why not either use `starttls', or do `tls' and = then > `network' if that fails? Lars already answered, but I'd like to comment on this: > After all, gnutls not being available is only > one of many possible failure modes, so it's better to just let > open-network-stream handle them. For the Windows port, having libgnutls-26.dll unavailable is not a failure; it's entirely parallel to the non-Windows ports being built withouth GnuTLS support. Checking that the library it is available should be totally equivalent (modulo the moment it happens) to a feature check or (if (fboundp 'whatever) ...). =C2=A0 =C2=A0 Juanma