From c150ffb220c15f10076b86fb2776a782a4d098ae Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Lo=C3=AFc=20Hoguin?=
Date: Tue, 24 Jan 2023 10:03:59 +0100
Subject: Gun 2.0
---
_build/content/articles/gun-2.0.0.asciidoc | 80 +++++
_build/data/projects/gun.toml | 4 +-
articles/asciideck/index.html | 4 +
articles/cowboy-2.0.0-pre.4/index.html | 4 +
articles/cowboy-2.0.0-rc.1/index.html | 4 +
articles/cowboy-2.0.0-rc.2/index.html | 4 +
articles/cowboy-2.0.0/index.html | 4 +
articles/cowboy-2.1.0/index.html | 4 +
articles/cowboy-2.2.0/index.html | 4 +
articles/cowboy-2.3.0/index.html | 4 +
articles/cowboy-2.4.0/index.html | 4 +
articles/cowboy-2.5.0/index.html | 4 +
articles/cowboy-2.6.0/index.html | 4 +
articles/cowboy-2.7.0/index.html | 4 +
articles/cowboy-2.8.0/index.html | 4 +
articles/cowboy-2.9.0/index.html | 4 +
articles/cowboy2-qs/index.html | 4 +
articles/dont-let-it-crash/index.html | 4 +
.../erlang-meetup-10-septembre-2019/index.html | 4 +
articles/erlang-scalability/index.html | 4 +
articles/erlang-validate-utf8/index.html | 4 +
articles/erlang.mk-and-relx/index.html | 4 +
.../index.html | 4 +
articles/erlanger-playbook/index.html | 4 +
articles/farwest-funded/index.html | 4 +
articles/github-sponsors/index.html | 4 +
articles/gun-1.0.0-rc.1/index.html | 4 +
articles/gun-1.0.0/index.html | 4 +
articles/gun-1.2.0/index.html | 4 +
articles/gun-1.3.0/index.html | 4 +
articles/gun-2.0.0-pre.1/index.html | 4 +
articles/gun-2.0.0-pre.2/index.html | 4 +
articles/gun-2.0.0-rc.1/index.html | 4 +
articles/gun-2.0.0/index.html | 355 +++++++++++++++++++++
articles/index.html | 38 ++-
articles/index.xml | 13 +-
articles/january-2014-status/index.html | 4 +
articles/joe_the_rubber_duck/index.html | 4 +
articles/merry-christmas-2018/index.html | 4 +
articles/merry-christmas-2019/index.html | 4 +
articles/ml-archives/index.html | 4 +
articles/on-open-source/index.html | 4 +
articles/page/2/index.html | 38 +--
articles/page/3/index.html | 18 ++
articles/ranch-1.3/index.html | 4 +
articles/ranch-1.6.0/index.html | 4 +
articles/ranch-1.7.0/index.html | 4 +
articles/ranch-2.0.0-rc.1/index.html | 4 +
articles/ranch-2.0.0/index.html | 4 +
articles/ranch-2.1.0/index.html | 4 +
articles/ranch-ftp/index.html | 4 +
articles/the-elephant-in-the-room/index.html | 4 +
articles/the-gateway-trilogy/index.html | 4 +
articles/the-story-so-far/index.html | 4 +
articles/tictactoe/index.html | 4 +
articles/website-update/index.html | 4 +
articles/xerl-0.1-empty-modules/index.html | 4 +
articles/xerl-0.2-two-modules/index.html | 4 +
articles/xerl-0.3-atomic-expressions/index.html | 4 +
articles/xerl-0.4-expression-separator/index.html | 4 +
articles/xerl-0.5-intermediate-module/index.html | 4 +
docs/en/gun/2.0/guide/introduction.asciidoc | 2 +-
docs/en/gun/2.0/guide/introduction/index.html | 2 +-
docs/en/gun/2.0/guide/migrating_from_1.3.asciidoc | 43 ++-
.../en/gun/2.0/guide/migrating_from_1.3/index.html | 22 +-
docs/index.xml | 2 +-
donate/index.html | 2 +
erlanger-playbook/index.html | 2 +
index.html | 4 +-
index.xml | 13 +-
services/index.html | 2 +
sitemap.xml | 7 +-
72 files changed, 814 insertions(+), 49 deletions(-)
create mode 100644 _build/content/articles/gun-2.0.0.asciidoc
create mode 100644 articles/gun-2.0.0/index.html
diff --git a/_build/content/articles/gun-2.0.0.asciidoc b/_build/content/articles/gun-2.0.0.asciidoc
new file mode 100644
index 00000000..79720bd9
--- /dev/null
+++ b/_build/content/articles/gun-2.0.0.asciidoc
@@ -0,0 +1,80 @@
++++
+date = "2023-01-24T07:00:00+01:00"
+title = "Gun 2.0"
+
++++
+
+Gun `2.0.0` has been released!
+
+Gun 2.0 adds a ton of features along with a small number
+of breaking changes.
+
+Gun 2.0 includes state of the art tunnel support. With
+Gun 2.0 it is possible to make requests or data go through
+any number of proxy endpoints using any combination of
+TCP or TLS transports and HTTP/1.1, HTTP/2 or SOCKS5
+protocols. All combinations of the scenario Proxy1 ->
+Proxy2 -> Origin are tested and known to work.
+
+You can watch a demo of the tunnel support below. This
+video is the first of its kind. If you like it, or you
+don't like it, please tell me! I intend to continue
+producing those on a semi-regular basis. Watch:
+
+++++
+
+++++
+
+Gun 2.0 can now be used to send and receive raw data,
+as if it was just a normal socket. This can be
+useful when needing to connect through a number
+of HTTP/SOCKS5 proxies, allowing the use of Gun's
+great proxying capabilities for non-Web protocols.
+This can also be useful when performing HTTP/1.1
+Upgrade to custom protocols.
+
+Gun 2.0 adds many more features such as Websocket over
+HTTP/2, Websocket protocol negotiation, a built-in
+cookie store, graceful shutdown, flow control for
+data messages, event handlers and more.
+
+Gun 2.0 greatly improves the HTTP/2 performance when it
+comes to receiving large response bodies; and when receiving
+response bodies from many separate requests concurrently.
+
+Gun 2.0 will be more responsive in the event of connection
+failures. It now checks return values from send calls and
+has send timeouts enabled by default. For HTTP/2 a new
+option allows Gun to drop the connection when pings do
+not get a response in a timely manner.
+
+Gun now shares much of its HTTP/2 code with Cowboy,
+including the HTTP/2 state machine. Numerous issues were
+fixed as a result because the Cowboy implementation was
+much more advanced.
+
+The Gun connection process is now implemented using `gen_statem`.
+
+The `gun_pool` module is a significant experimental feature
+that allows users to create pools of connections. Pools
+are split by authority and a user-provided token, allowing
+users to reuse connections in a similar way to what Web
+browsers are doing. Please check it out and provide feedback!
+
+Gun 2.0 requires Erlang/OTP 22.0 or greater and is tested
+and supported on Linux, macOS and Windows.
+
+A complete
+list of changes can be found in the migration guide:
+https://ninenines.eu/docs/en/gun/2.0/guide/migrating_from_1.3/[Migrating from Gun 1.3 to 2.0].
+
+I will now focus on implementing HTTP/3 and QUIC, first
+in Cowboy and then in Gun.
+
+You can donate to this project via
+https://github.com/sponsors/essen[GitHub Sponsors].
+
+As usual, feedback is appreciated, and issues or
+questions should be sent via Github tickets. Thanks!
diff --git a/_build/data/projects/gun.toml b/_build/data/projects/gun.toml
index 79280d82..a777d713 100644
--- a/_build/data/projects/gun.toml
+++ b/_build/data/projects/gun.toml
@@ -1,10 +1,10 @@
title = "Gun"
catchphrase = "The smoking gun of HTTP clients."
-description = "Asynchronous, always-connected client with support for HTTP/1.1, HTTP/2 and Websocket."
+description = "Asynchronous client with support for HTTP/1.1, HTTP/2, Websocket and more."
name = "gun"
repository = "https://github.com/ninenines/gun"
versions = ["2.0", "1.3", "1.2", "1.1", "1.0"]
-branches = ["master", "1.3.1", "1.2.0", "1.1.0", "1.0.0"]
+branches = ["2.0.0", "1.3.1", "1.2.0", "1.1.0", "1.0.0"]
has_source = true
has_guide = true
has_manual = true
diff --git a/articles/asciideck/index.html b/articles/asciideck/index.html
index 60a1708f..1ad52960 100644
--- a/articles/asciideck/index.html
+++ b/articles/asciideck/index.html
@@ -109,6 +109,10 @@ http://www.gnu.org/software/src-highlite -->
+
Gun 2.0 adds a ton of features along with a small number of breaking changes.
+
Gun 2.0 includes state of the art tunnel support. With Gun 2.0 it is possible to make requests or data go through any number of proxy endpoints using any combination of TCP or TLS transports and HTTP/1.1, HTTP/2 or SOCKS5 protocols. All combinations of the scenario Proxy1 -> Proxy2 -> Origin are tested and known to work.
+
You can watch a demo of the tunnel support below. This video is the first of its kind. If you like it, or you don't like it, please tell me! I intend to continue producing those on a semi-regular basis. Watch:
+
Gun 2.0 can now be used to send and receive raw data, as if it was just a normal socket. This can be useful when needing to connect through a number of HTTP/SOCKS5 proxies, allowing the use of Gun's great proxying capabilities for non-Web protocols. This can also be useful when performing HTTP/1.1 Upgrade to custom protocols.
+
Gun 2.0 adds many more features such as Websocket over HTTP/2, Websocket protocol negotiation, a built-in cookie store, graceful shutdown, flow control for data messages, event handlers and more.
+
Gun 2.0 greatly improves the HTTP/2 performance when it comes to receiving large response bodies; and when receiving response bodies from many separate requests concurrently.
+
Gun 2.0 will be more responsive in the event of connection failures. It now checks return values from send calls and has send timeouts enabled by default. For HTTP/2 a new option allows Gun to drop the connection when pings do not get a response in a timely manner.
+
Gun now shares much of its HTTP/2 code with Cowboy, including the HTTP/2 state machine. Numerous issues were fixed as a result because the Cowboy implementation was much more advanced.
+
The Gun connection process is now implemented using gen_statem.
+
The gun_pool module is a significant experimental feature that allows users to create pools of connections. Pools are split by authority and a user-provided token, allowing users to reuse connections in a similar way to what Web browsers are doing. Please check it out and provide feedback!
+
Gun 2.0 requires Erlang/OTP 22.0 or greater and is tested and supported on Linux, macOS and Windows.
Gun 2.0.0 has been released!
+Gun 2.0 adds a ton of features along with a small number of breaking changes.
+Gun 2.0 includes state of the art tunnel support. With Gun 2.0 it is possible to make requests or data go through any number of proxy endpoints using any combination of TCP or TLS transports and HTTP/1.1, HTTP/2 or SOCKS5 protocols. All combinations of the scenario Proxy1 -> Proxy2 -> Origin are tested and known to work.
Gun 1.2.0 has been released!
-Gun is an HTTP/1.1, HTTP/2 and Websocket client for Erlang/OTP.
-Gun now supports issuing CONNECT requests to HTTP proxies in order to establish tunnels to origin servers. Gun can establish tunnels over one or more proxies as necessary.
-All existing protocols can be used inside the tunnel, including HTTP/1.1, HTTP/2 and Websocket over both TCP and TLS connections.
-Note that it is currently not possible to tunnel a TLS connection via an HTTPS proxy due to limitations in the current version of Erlang/OTP.