unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Thomas Fitzsimmons <fitzsim@fitzsim.org>
To: "João Távora" <joaotavora@gmail.com>
Cc: emacs-devel <emacs-devel@gnu.org>
Subject: Re: [GNU ELPA] New package: url-http-oauth
Date: Mon, 08 May 2023 11:27:38 -0400	[thread overview]
Message-ID: <m3a5yeyhat.fsf@fitzsim.org> (raw)
In-Reply-To: <CALDnm50G3cbOnxHUBdUCVHn0T=1apBcpiy5hgohikA60GOUyZQ@mail.gmail.com> ("João Távora"'s message of "Mon, 8 May 2023 08:50:06 +0100")

Hi João,

João Távora <joaotavora@gmail.com> writes:

> I think packages such as this one are very welcome, and I appreciate the
> UI-agnostic architecture you describe.

Thanks.

> Url.el itself, last i looked, seemed a bit outdated and hard to work
> with.

I find it OK to work with.  It's primarily elisp, vs some other
proposals I've seen, so I can step through most of it with edebug.
There's one FIXME in url-http-oauth currently that may represent a
url.el oddity (or may represent me doing something wrong):

;; FIXME: if anything goes wrong during the authentication steps,
;; `url-http-end-of-document-sentinel' calls back into
;; `url-oauth-auth' somehow.  Maybe `url-http-no-retry' can help here?

I'm sure other client libraries would have oddities too though.

Are there bugs filed for the specific ways in which url.el may be
outdated or hard to work with?  Maybe someone could maintain a
collection of links to those bug reports, to see how contenders measure
up?  Of course, that list wouldn't represent the upsides of url.el, such
as the elisp purity I mentioned.

> Are there other http client libraries for Emacs?

Today url.el works for me, so I don't have plans to change; I'll
probably just follow what makes it into Emacs core.

> Could they also take advantage of your new library?

If the new library implemented url.el's APIs, then sure.  I would accept
well-defined/minimal compatibility patches for other client libraries
too, of course.

Thomas



  parent reply	other threads:[~2023-05-08 15:27 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
2023-05-08 15:27   ` Thomas Fitzsimmons [this message]
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=m3a5yeyhat.fsf@fitzsim.org \
    --to=fitzsim@fitzsim.org \
    --cc=emacs-devel@gnu.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).