unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
* http/2
@ 2017-01-22 17:27 Lars Ingebrigtsen
  2017-01-22 17:37 ` http/2 Stefan Monnier
  0 siblings, 1 reply; 9+ messages in thread
From: Lars Ingebrigtsen @ 2017-01-22 17:27 UTC (permalink / raw)
  To: emacs-devel

I googled around a bit to see whether anybody's implemented http/2 for
Emacs.  I guess there's no immediate need, really, but eventually web
servers are going to switch to http/2-only, I guess.

Has anybody looked into implementing it?  The spec is horrible and
unwieldy, so I can imagine people just backing away from it in horror,
but...  It's a challenge!

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





^ permalink raw reply	[flat|nested] 9+ messages in thread

* Re: http/2
  2017-01-22 17:27 http/2 Lars Ingebrigtsen
@ 2017-01-22 17:37 ` Stefan Monnier
  2017-01-22 18:07   ` http/2 Lars Ingebrigtsen
  0 siblings, 1 reply; 9+ messages in thread
From: Stefan Monnier @ 2017-01-22 17:37 UTC (permalink / raw)
  To: emacs-devel

> Has anybody looked into implementing it?  The spec is horrible and
> unwieldy, so I can imagine people just backing away from it in horror,
> but...  It's a challenge!

I think in the context of Emacs, "implementing" it, will mean "provide
bindings to a libhttp2 library".  Ideally as a dynlink module.


        Stefan




^ permalink raw reply	[flat|nested] 9+ messages in thread

* Re: http/2
  2017-01-22 17:37 ` http/2 Stefan Monnier
@ 2017-01-22 18:07   ` Lars Ingebrigtsen
  0 siblings, 0 replies; 9+ messages in thread
From: Lars Ingebrigtsen @ 2017-01-22 18:07 UTC (permalink / raw)
  To: Stefan Monnier; +Cc: emacs-devel

Stefan Monnier <monnier@iro.umontreal.ca> writes:

> I think in the context of Emacs, "implementing" it, will mean "provide
> bindings to a libhttp2 library".  Ideally as a dynlink module.

I think it would be feasible to implement in Emacs Lisp for somebody who
finds binary twiddling in Emacs amusing.  (I can't imagine who.)  Or is
there anything in particular that makes that... unlikely?

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no



^ permalink raw reply	[flat|nested] 9+ messages in thread

* HTTP/2
@ 2020-10-02  2:55 Lars Ingebrigtsen
  2020-10-02 13:08 ` HTTP/2 Robert Pluim
  0 siblings, 1 reply; 9+ messages in thread
From: Lars Ingebrigtsen @ 2020-10-02  2:55 UTC (permalink / raw)
  To: emacs-devel

Emacs will have to implement HTTP/2 one way or another.  Few people have
disabled HTTP 1.x on their servers, but it's going to happen, so I'd
rather see HTTP/2 (and HTTP/3?) support in Emacs sooner rather than
later.

Not, implementing HTTP/2 in Emacs Lisp sounds like a fun and interesting
project, but...  it's probably too much fun?  So using an existing
well-supported HTTP/2 library (preferably one that already uses GnuTLS,
I guess?) is probably the way forward.

Has anybody looked at this?  I have done absolutely no research here --
are there a bunch of suitable HTTP/2 libraries we could consider?  Or
even one?

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no




^ permalink raw reply	[flat|nested] 9+ messages in thread

* Re: HTTP/2
  2020-10-02  2:55 HTTP/2 Lars Ingebrigtsen
@ 2020-10-02 13:08 ` Robert Pluim
  2020-10-04 17:07   ` HTTP/2 Helmut Eller
  0 siblings, 1 reply; 9+ messages in thread
From: Robert Pluim @ 2020-10-02 13:08 UTC (permalink / raw)
  To: Lars Ingebrigtsen; +Cc: emacs-devel

>>>>> 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
-- 



^ permalink raw reply	[flat|nested] 9+ messages in thread

* Re: HTTP/2
  2020-10-02 13:08 ` HTTP/2 Robert Pluim
@ 2020-10-04 17:07   ` Helmut Eller
  2020-10-04 17:19     ` HTTP/2 Eli Zaretskii
  0 siblings, 1 reply; 9+ messages in thread
From: Helmut Eller @ 2020-10-04 17:07 UTC (permalink / raw)
  To: emacs-devel

On Fri, Oct 02 2020, Robert Pluim wrote:

>>>>>> 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
>     Lars> 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
>     Lars> interesting
>     Lars> project, but...  it's probably too much fun?  So using an existing
>     Lars> well-supported HTTP/2 library (preferably one that already
>     Lars> 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.

I'd rather see bindings for libcurl directly.  In particular something
that integrates libcurl's "multi handles" with Emacs' event loop.

Helmut




^ permalink raw reply	[flat|nested] 9+ messages in thread

* Re: HTTP/2
  2020-10-04 17:07   ` HTTP/2 Helmut Eller
@ 2020-10-04 17:19     ` Eli Zaretskii
  2020-10-04 17:57       ` HTTP/2 Helmut Eller
  0 siblings, 1 reply; 9+ messages in thread
From: Eli Zaretskii @ 2020-10-04 17:19 UTC (permalink / raw)
  To: Helmut Eller; +Cc: emacs-devel

> From: Helmut Eller <eller.helmut@gmail.com>
> Date: Sun, 04 Oct 2020 19:07:57 +0200
> 
> > libcurl uses nghttp2 for its HTTP/2 support, and it can use GnuTLS, so
> > we can steal^winspire our implementation from that.
> 
> I'd rather see bindings for libcurl directly.

Why?



^ permalink raw reply	[flat|nested] 9+ messages in thread

* Re: HTTP/2
  2020-10-04 17:19     ` HTTP/2 Eli Zaretskii
@ 2020-10-04 17:57       ` Helmut Eller
  2020-10-04 18:29         ` HTTP/2 Eli Zaretskii
  0 siblings, 1 reply; 9+ messages in thread
From: Helmut Eller @ 2020-10-04 17:57 UTC (permalink / raw)
  To: Eli Zaretskii; +Cc: emacs-devel

On Sun, Oct 04 2020, Eli Zaretskii wrote:

>> From: Helmut Eller <eller.helmut@gmail.com>
>> Date: Sun, 04 Oct 2020 19:07:57 +0200
>> 
>> > libcurl uses nghttp2 for its HTTP/2 support, and it can use GnuTLS, so
>> > we can steal^winspire our implementation from that.
>> 
>> I'd rather see bindings for libcurl directly.
>
> Why?

Because libcurl supports many other protocols, e.g. SCP.  Maybe nghttp2
would be useful, if somebody wanted to implement a HTTP/2 server.

Helmut



^ permalink raw reply	[flat|nested] 9+ messages in thread

* Re: HTTP/2
  2020-10-04 17:57       ` HTTP/2 Helmut Eller
@ 2020-10-04 18:29         ` Eli Zaretskii
  0 siblings, 0 replies; 9+ messages in thread
From: Eli Zaretskii @ 2020-10-04 18:29 UTC (permalink / raw)
  To: Helmut Eller; +Cc: emacs-devel

> From: Helmut Eller <eller.helmut@gmail.com>
> Cc: emacs-devel@gnu.org
> Date: Sun, 04 Oct 2020 19:57:19 +0200
> 
> >> I'd rather see bindings for libcurl directly.
> >
> > Why?
> 
> Because libcurl supports many other protocols, e.g. SCP.

If someone needs those other protocols, they can always develop an
Emacs module which used libcurl.  That is not a reason good enough to
have yet another dependency library for building Emacs.  For that, we
need to carefully consider which protocols we really need and what
for, and only add another library if we really use a large fraction of
its capabilities.  IMO, at least.



^ permalink raw reply	[flat|nested] 9+ messages in thread

end of thread, other threads:[~2020-10-04 18:29 UTC | newest]

Thread overview: 9+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2020-10-02  2:55 HTTP/2 Lars Ingebrigtsen
2020-10-02 13:08 ` HTTP/2 Robert Pluim
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

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).