emacs-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [GNU ELPA] New package: url-http-oauth


From: T.V Raman
Subject: Re: [GNU ELPA] New package: url-http-oauth
Date: Mon, 8 May 2023 09:44:53 -0700

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  🦮



reply via email to

[Prev in Thread] Current Thread [Next in Thread]