summaryrefslogtreecommitdiffstats
path: root/articles/cowboy-2.4.0/index.html
diff options
context:
space:
mode:
authorLoïc Hoguin <[email protected]>2018-06-13 09:54:12 +0200
committerLoïc Hoguin <[email protected]>2018-06-13 09:54:12 +0200
commit92b54aacc0de5446dd5497c39897b0bbff72e626 (patch)
treec3a98cfec636d1271f5804e5c19b35b208bba00d /articles/cowboy-2.4.0/index.html
parent8b5c3dc972b99f174750123c9e4abc96259c34a9 (diff)
downloadninenines.eu-92b54aacc0de5446dd5497c39897b0bbff72e626.tar.gz
ninenines.eu-92b54aacc0de5446dd5497c39897b0bbff72e626.tar.bz2
ninenines.eu-92b54aacc0de5446dd5497c39897b0bbff72e626.zip
Rebuild using Asciideck
Diffstat (limited to 'articles/cowboy-2.4.0/index.html')
-rw-r--r--articles/cowboy-2.4.0/index.html36
1 files changed, 8 insertions, 28 deletions
diff --git a/articles/cowboy-2.4.0/index.html b/articles/cowboy-2.4.0/index.html
index cae198b2..2c035ff8 100644
--- a/articles/cowboy-2.4.0/index.html
+++ b/articles/cowboy-2.4.0/index.html
@@ -69,34 +69,14 @@
</p>
</header>
-<div class="paragraph"><p>Cowboy <code>2.4.0</code> has been released!</p></div>
-<div class="paragraph"><p>Numerous HTTP/2 options have been added to control
-the HTTP/2 SETTINGS and general behavior of HTTP/2
-connections. The options for initial window sizes,
-maximum frame sizes or compression table sizes
-might be of interest for optimizing the performance
-of HTTP/2 connections.</p></div>
-<div class="paragraph"><p>Experimental support for Websocket over HTTP/2 was
-added. Note that browsers do not currently support
-it. The only browser with partial support is Google
-Chrome 67 (dev build) started with a specific flag.
-As a result it&#8217;s disabled by default in Cowboy too.</p></div>
-<div class="paragraph"><p>All of Cowboy&#8217;s RFC7540 tests and all of the h2spec
-test suite cases now pass. There are still parts
-that are not implemented (the priority mechanisms
-for example) and edge cases that are not covered,
-however, so the HTTP/2 support can still be improved.</p></div>
-<div class="paragraph"><p>A complete
-list of changes can be found in the migration guide:
-<a href="https://ninenines.eu/docs/en/cowboy/2.4/guide/migrating_from_2.3/">Migrating from Cowboy 2.3 to 2.4</a>.</p></div>
-<div class="paragraph"><p>You can donate to this project via
-<a href="https://salt.bountysource.com/teams/ninenines">BountySource</a>.
-These funds are used to pay for additional servers for
-testing. A new server was added this month and allows
-me to test with additional Linux distributions Alpine,
-CentOS and Debian. Thanks in advance!</p></div>
-<div class="paragraph"><p>As usual, feedback is appreciated, and issues or
-questions should be sent via Github tickets. Thanks!</p></div>
+<p>Cowboy <code>2.4.0</code> has been released!</p>
+<p>Numerous HTTP/2 options have been added to control the HTTP/2 SETTINGS and general behavior of HTTP/2 connections. The options for initial window sizes, maximum frame sizes or compression table sizes might be of interest for optimizing the performance of HTTP/2 connections.</p>
+<p>Experimental support for Websocket over HTTP/2 was added. Note that browsers do not currently support it. The only browser with partial support is Google Chrome 67 (dev build) started with a specific flag. As a result it&apos;s disabled by default in Cowboy too.</p>
+<p>All of Cowboy&apos;s RFC7540 tests and all of the h2spec test suite cases now pass. There are still parts that are not implemented (the priority mechanisms for example) and edge cases that are not covered, however, so the HTTP/2 support can still be improved.</p>
+<p>A complete list of changes can be found in the migration guide: <a href="https://ninenines.eu/docs/en/cowboy/2.4/guide/migrating_from_2.3/">Migrating from Cowboy 2.3 to 2.4</a>.</p>
+<p>You can donate to this project via <a href="https://salt.bountysource.com/teams/ninenines">BountySource</a>. These funds are used to pay for additional servers for testing. A new server was added this month and allows me to test with additional Linux distributions Alpine, CentOS and Debian. Thanks in advance!</p>
+<p>As usual, feedback is appreciated, and issues or questions should be sent via Github tickets. Thanks!</p>
+
</article>
</div>