From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: [ELPA] New package: plz Date: Wed, 11 May 2022 19:55:32 -0400 Message-ID: References: <17c31efc-33ff-db74-3a10-e8861f3c4622@alphapapa.net> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="25122"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/29.0.50 (gnu/linux) Cc: emacs-devel@gnu.org To: Adam Porter Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Thu May 12 01:58:10 2022 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nowDa-0006Jh-0C for ged-emacs-devel@m.gmane-mx.org; Thu, 12 May 2022 01:58:10 +0200 Original-Received: from localhost ([::1]:44520 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1nowDY-00041U-Fj for ged-emacs-devel@m.gmane-mx.org; Wed, 11 May 2022 19:58:08 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:39964) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nowBJ-0001Dd-BH for emacs-devel@gnu.org; Wed, 11 May 2022 19:55:49 -0400 Original-Received: from mailscanner.iro.umontreal.ca ([132.204.25.50]:56560) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nowBG-00084P-De for emacs-devel@gnu.org; Wed, 11 May 2022 19:55:47 -0400 Original-Received: from pmg1.iro.umontreal.ca (localhost.localdomain [127.0.0.1]) by pmg1.iro.umontreal.ca (Proxmox) with ESMTP id 5F7461002CB; Wed, 11 May 2022 19:55:44 -0400 (EDT) Original-Received: from mail01.iro.umontreal.ca (unknown [172.31.2.1]) by pmg1.iro.umontreal.ca (Proxmox) with ESMTP id CAF2010010F; Wed, 11 May 2022 19:55:41 -0400 (EDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=iro.umontreal.ca; s=mail; t=1652313341; bh=lalYSD/ZjdZNHr/Po2Kx7xXylItxbLd9OBe7tllp5D0=; h=From:To:Cc:Subject:References:Date:In-Reply-To:From; b=JGQ3H5raBGYVs/7D9i2qEOkmRAZKb6OTaGWHgyBE+653R9RuFKtGrwV+160P6puyT 0teZLEWmOUNitRlFfFKpKbIDrA6/k0u2zqLD+qzajeXZoFwBqOfWQFjyXNKtpvyQqB XI21USvbFFw0tkrclX/WDQz7X3QTdKMmOC9pBS459iQZHGgY2TAu6/bHTR6nmoaQ5f tHaEoJ8PoHSxq8qrZpYkI5qAh32yvckQEybQIT6Uz6PuVOboW0IJOoEz2ZJSG7WXSc X68igUjxSmahEqC9mqHyVOY6sI/MAu6fuyeewR6/LDvUA+5ClaEDFdI7vt6K1Li9UV oARMXV9SK6dXQ== Original-Received: from pastel (unknown [45.72.221.51]) by mail01.iro.umontreal.ca (Postfix) with ESMTPSA id 8C5AC1206EB; Wed, 11 May 2022 19:55:41 -0400 (EDT) In-Reply-To: <17c31efc-33ff-db74-3a10-e8861f3c4622@alphapapa.net> (Adam Porter's message of "Wed, 11 May 2022 17:30:26 -0500") Received-SPF: pass client-ip=132.204.25.50; envelope-from=monnier@iro.umontreal.ca; helo=mailscanner.iro.umontreal.ca X-Spam_score_int: -42 X-Spam_score: -4.3 X-Spam_bar: ---- X-Spam_report: (-4.3 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 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-mx.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.io gmane.emacs.devel:289653 Archived-At: >>> It's an HTTP library that uses Curl as a backend. >> I hope we can consolidate this with `request.el` and `url.el` sooner >> rather than later. > I'm not sure what that would entail. Each library is very different > from the others, both in terms of API and--especially--internally. E.g.: - wrappers that provide request.el's API while using plz internally. - A `url.el` backend for plz. - A plz backend the `url-retrieve`. >> As others mentioned, adding a backend to plz which uses url.el (or at >> least doesn't require `curl` to be installed) would be great. > Using url.el internally would inherit its problems, defeating the > purpose of plz.el. I don't think so. It would mean only that you'd suffer from those problems if `curl` is not installed, while still benefiting from a better API. `url.el` has its share of problems, but let's not forget that it works well enough in many cases. A `url.el` backend doesn't involve fixing its limitations. It just means that code can use the plz API (and presumably benefit from the more reliable behavior when `curl` is available) while still working as well as before when `curl` is not installed. > But it could develop its own, non-curl-based backend... I assumed that reusing url.el code should be easier than rewriting all of it from scratch, but yes, the most important thing is to match `url.el`s current killer feature which is that it works well enough in many important cases without relying on any third party application. Stefan