Update Hugo, docs

1 files changed, 68 insertions, 65 deletions

diff --git a/docs/en/cowboy/2.0/guide/ws_protocol/index.html b/docs/en/cowboy/2.0/guide/ws_protocol/index.html
index 38b754b0..d70fe10d 100644
--- a/docs/en/cowboy/2.0/guide/ws_protocol/index.html
+++ b/docs/en/cowboy/2.0/guide/ws_protocol/index.html
@@ -7,7 +7,7 @@
     <meta name="description" content="">
     <meta name="author" content="Loïc Hoguin based on a design from (Soft10) Pol Cámara">
 
-    <meta name="generator" content="Hugo 0.17" />
+    <meta name="generator" content="Hugo 0.26" />
 
     <title>Nine Nines: The Websocket protocol</title>
 
@@ -67,76 +67,79 @@
 
 <h1 class="lined-header"><span>The Websocket protocol</span></h1>
 
-<div class="paragraph"><p>This chapter explains what Websocket is and why it is

-a vital component of soft realtime Web applications.</p></div>

-<div class="sect1">

-<h2 id="_description">Description</h2>

-<div class="sectionbody">

-<div class="paragraph"><p>Websocket is an extension to HTTP that emulates plain TCP

-connections between the client, typically a Web browser,

-and the server. It uses the HTTP Upgrade mechanism to

-establish the connection.</p></div>

-<div class="paragraph"><p>Websocket connections are fully asynchronous, unlike

-HTTP/1.1 (synchronous) and HTTP/2 (asynchronous, but the

-server can only initiate streams in response to requests).

-With Websocket, the client and the server can both send

-frames at any time without any restriction. It is closer

-to TCP than any of the HTTP protocols.</p></div>

-<div class="paragraph"><p>Websocket is an IETF standard. Cowboy supports the standard

-and all drafts that were previously implemented by browsers,

-excluding the initial flawed draft sometimes known as

-"version 0".</p></div>

-</div>

-</div>

-<div class="sect1">

-<h2 id="_websocket_vs_http_2">Websocket vs HTTP/2</h2>

-<div class="sectionbody">

-<div class="paragraph"><p>For a few years Websocket was the only way to have a

-bidirectional asynchronous connection with the server.

-This changed when HTTP/2 was introduced. While HTTP/2

-requires the client to first perform a request before

-the server can push data, this is only a minor restriction

-as the client can do so just as it connects.</p></div>

-<div class="paragraph"><p>Websocket was designed as a kind-of-TCP channel to a

-server. It only defines the framing and connection

-management and lets the developer implement a protocol

-on top of it. For example you could implement IRC over

-Websocket and use a Javascript IRC client to speak to

-the server.</p></div>

-<div class="paragraph"><p>HTTP/2 on the other hand is just an improvement over

-the HTTP/1.1 connection and request/response mechanism.

-It has the same semantics as HTTP/1.1.</p></div>

-<div class="paragraph"><p>If all you need is to access an HTTP API, then HTTP/2

-should be your first choice. On the other hand, if what

-you need is a different protocol, then you can use

-Websocket to implement it.</p></div>

-</div>

-</div>

-<div class="sect1">

-<h2 id="_implementation">Implementation</h2>

-<div class="sectionbody">

-<div class="paragraph"><p>Cowboy implements Websocket as a protocol upgrade. Once the

-upgrade is performed from the <code>init/2</code> callback, Cowboy

-switches to Websocket. Please consult the next chapter for

-more information on initiating and handling Websocket

-connections.</p></div>

-<div class="paragraph"><p>The implementation of Websocket in Cowboy is validated using

-the Autobahn test suite, which is an extensive suite of tests

-covering all aspects of the protocol. Cowboy passes the

-suite with 100% success, including all optional tests.</p></div>

-<div class="paragraph"><p>Cowboy&#8217;s Websocket implementation also includes the

-permessage-deflate and x-webkit-deflate-frame compression

-extensions.</p></div>

-<div class="paragraph"><p>Cowboy will automatically use compression when the

-<code>compress</code> option is returned from the <code>init/2</code> function.</p></div>

-</div>

-</div>

+<div class="paragraph"><p>This chapter explains what Websocket is and why it is
+a vital component of soft realtime Web applications.</p></div>
+<div class="sect1">
+<h2 id="_description">Description</h2>
+<div class="sectionbody">
+<div class="paragraph"><p>Websocket is an extension to HTTP that emulates plain TCP
+connections between the client, typically a Web browser,
+and the server. It uses the HTTP Upgrade mechanism to
+establish the connection.</p></div>
+<div class="paragraph"><p>Websocket connections are fully asynchronous, unlike
+HTTP/1.1 (synchronous) and HTTP/2 (asynchronous, but the
+server can only initiate streams in response to requests).
+With Websocket, the client and the server can both send
+frames at any time without any restriction. It is closer
+to TCP than any of the HTTP protocols.</p></div>
+<div class="paragraph"><p>Websocket is an IETF standard. Cowboy supports the standard
+and all drafts that were previously implemented by browsers,
+excluding the initial flawed draft sometimes known as
+"version 0".</p></div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="_websocket_vs_http_2">Websocket vs HTTP/2</h2>
+<div class="sectionbody">
+<div class="paragraph"><p>For a few years Websocket was the only way to have a
+bidirectional asynchronous connection with the server.
+This changed when HTTP/2 was introduced. While HTTP/2
+requires the client to first perform a request before
+the server can push data, this is only a minor restriction
+as the client can do so just as it connects.</p></div>
+<div class="paragraph"><p>Websocket was designed as a kind-of-TCP channel to a
+server. It only defines the framing and connection
+management and lets the developer implement a protocol
+on top of it. For example you could implement IRC over
+Websocket and use a Javascript IRC client to speak to
+the server.</p></div>
+<div class="paragraph"><p>HTTP/2 on the other hand is just an improvement over
+the HTTP/1.1 connection and request/response mechanism.
+It has the same semantics as HTTP/1.1.</p></div>
+<div class="paragraph"><p>If all you need is to access an HTTP API, then HTTP/2
+should be your first choice. On the other hand, if what
+you need is a different protocol, then you can use
+Websocket to implement it.</p></div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="_implementation">Implementation</h2>
+<div class="sectionbody">
+<div class="paragraph"><p>Cowboy implements Websocket as a protocol upgrade. Once the
+upgrade is performed from the <code>init/2</code> callback, Cowboy
+switches to Websocket. Please consult the next chapter for
+more information on initiating and handling Websocket
+connections.</p></div>
+<div class="paragraph"><p>The implementation of Websocket in Cowboy is validated using
+the Autobahn test suite, which is an extensive suite of tests
+covering all aspects of the protocol. Cowboy passes the
+suite with 100% success, including all optional tests.</p></div>
+<div class="paragraph"><p>Cowboy&#8217;s Websocket implementation also includes the
+permessage-deflate and x-webkit-deflate-frame compression
+extensions.</p></div>
+<div class="paragraph"><p>Cowboy will automatically use compression when the
+<code>compress</code> option is returned from the <code>init/2</code> function.</p></div>
+</div>
+</div>
 
 
 
 	
 		
 		
+		
+		
+		
 
 		<nav style="margin:1em 0">