unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "T.V Raman" <raman@google.com>
To: joaotavora@gmail.com
Cc: raman@google.com, fitzsim@fitzsim.org, emacs-devel@gnu.org
Subject: Re: [GNU ELPA] New package: url-http-oauth
Date: Mon, 8 May 2023 09:44:53 -0700	[thread overview]
Message-ID: <25689.9989.71356.660833@retriever.mtv.corp.google.com> (raw)
In-Reply-To: <CALDnm51+97LhoO42amH7PqBg-3EaKRLWfvntfAct+Wh9gkZA_A@mail.gmail.com>

I agree that using libcurl would be better, but that proposal has gone
nowhere. plz uses curl s a separate process but it might be a good
stepping stone to  eventually moving to a libcurl based solution.


João Távora writes:
 > On Mon, May 8, 2023 at 3:22 PM T.V Raman <raman@google.com> wrote:
 > >
 > >
 > > url.el is definitely outdated and  likely one of the bottlenecks that
 > > holds back EWW; the other is of course JS.
 > >
 > > I looked at plz.el when it came out and it is nice; by  depending on
 > > Curl, it immediately brings Emacs up-to-date with various URL bits that
 > > have languished in url.el. That said, for Emacs to be able to move on
 > > from url.el, I suspect we'll need an 80/20 plz wrapper that if loaded by
 > > the user causes calls to the url library to be overridden by plz so that
 > > one can then use EWW to validate the effectiveness and completeness of
 > > plz.
 > 
 > Hmm, OK, thanks for mentioning this.  Does it depend on curl or libcurl?
 > Starting a new process for every request seems not ideal, and
 > defeats the purpose of HTTP keep-alive.  But I'm just speculating
 > here, maybe that's not how it works.
 > 
 > An elisp HTTP client based on process-filters shouldn't be _that_
 > hard to write though.  AFAIR the ugly bits of url.el weren't about
 > that, but just run-of-the-mill API quirks about response codes and
 > such.
 > 
 > João

-- 

Thanks,

--Raman(I Search, I Find, I Misplace, I Research)
♉ Id: kg:/m/0285kf1  🦮

--

Thanks,

--Raman(I Search, I Find, I Misplace, I Research)
♉ Id: kg:/m/0285kf1  🦮



  parent reply	other threads:[~2023-05-08 16:44 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-06  5:07 [GNU ELPA] New package: url-http-oauth Thomas Fitzsimmons
2023-05-07 15:55 ` Philip Kaludercic
2023-05-08  7:50 ` João Távora
2023-05-08 10:30   ` Philip Kaludercic
2023-05-08 14:22   ` T.V Raman
2023-05-08 16:19     ` João Távora
2023-05-08 16:26       ` Eli Zaretskii
2023-05-08 16:44       ` T.V Raman [this message]
2023-05-08 15:27   ` Thomas Fitzsimmons
2023-05-08 17:03     ` João Távora

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=25689.9989.71356.660833@retriever.mtv.corp.google.com \
    --to=raman@google.com \
    --cc=emacs-devel@gnu.org \
    --cc=fitzsim@fitzsim.org \
    --cc=joaotavora@gmail.com \
    /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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).