From: Robert Pluim <rpluim@gmail.com>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: emacs-devel@gnu.org
Subject: Re: HTTP/2
Date: Fri, 02 Oct 2020 15:08:23 +0200 [thread overview]
Message-ID: <m24knckc6w.fsf@gmail.com> (raw)
In-Reply-To: <87o8llwd35.fsf@gnus.org> (Lars Ingebrigtsen's message of "Fri, 02 Oct 2020 04:55:58 +0200")
>>>>> On Fri, 02 Oct 2020 04:55:58 +0200, Lars Ingebrigtsen <larsi@gnus.org> said:
Lars> Emacs will have to implement HTTP/2 one way or another. Few people have
Lars> disabled HTTP 1.x on their servers, but it's going to happen, so I'd
Lars> rather see HTTP/2 (and HTTP/3?) support in Emacs sooner rather than
Lars> later.
Lars> Not, implementing HTTP/2 in Emacs Lisp sounds like a fun and interesting
Lars> project, but... it's probably too much fun? So using an existing
Lars> well-supported HTTP/2 library (preferably one that already uses GnuTLS,
Lars> I guess?) is probably the way forward.
libcurl uses nghttp2 for its HTTP/2 support, and it can use GnuTLS, so
we can steal^winspire our implementation from that.
Lars> Has anybody looked at this? I have done absolutely no research here --
Lars> are there a bunch of suitable HTTP/2 libraries we could consider? Or
Lars> even one?
Based on my whole 5 mins of research, thereʼs at least one, and if
itʼs good enough for curl I guess itʼs good enough for us.
BTW, nghttp2 is MIT-licensed, would that be an issue? wget2, which is
GLPv3-or-later can use nghttp2 as well.
Robert
--
next prev parent reply other threads:[~2020-10-02 13:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-02 2:55 HTTP/2 Lars Ingebrigtsen
2020-10-02 13:08 ` Robert Pluim [this message]
2020-10-04 17:07 ` HTTP/2 Helmut Eller
2020-10-04 17:19 ` HTTP/2 Eli Zaretskii
2020-10-04 17:57 ` HTTP/2 Helmut Eller
2020-10-04 18:29 ` HTTP/2 Eli Zaretskii
-- strict thread matches above, loose matches on Subject: below --
2017-01-22 17:27 http/2 Lars Ingebrigtsen
2017-01-22 17:37 ` http/2 Stefan Monnier
2017-01-22 18:07 ` http/2 Lars Ingebrigtsen
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m24knckc6w.fsf@gmail.com \
--to=rpluim@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=larsi@gnus.org \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.