summaryrefslogtreecommitdiffstats
path: root/docs/en/ranch/1.5/guide/parsers/index.html
diff options
context:
space:
mode:
Diffstat (limited to 'docs/en/ranch/1.5/guide/parsers/index.html')
-rw-r--r--docs/en/ranch/1.5/guide/parsers/index.html6
1 files changed, 3 insertions, 3 deletions
diff --git a/docs/en/ranch/1.5/guide/parsers/index.html b/docs/en/ranch/1.5/guide/parsers/index.html
index 3ab7d9b3..b5d2ddcf 100644
--- a/docs/en/ranch/1.5/guide/parsers/index.html
+++ b/docs/en/ranch/1.5/guide/parsers/index.html
@@ -76,7 +76,7 @@
<p>Text protocols are generally line based. This means that we can&apos;t do anything with them until we receive the full line.</p>
<p>A simple way to get a full line is to use <code>binary:split/{2,3}</code>.</p>
<div class="listingblock"><div class="title">Using binary:split/2 to get a line of input</div>
-<div class="content"><!-- Generator: GNU source-highlight 3.1.8
+<div class="content"><!-- Generator: GNU source-highlight 3.1.9
by Lorenzo Bettini
http://www.lorenzobettini.it
http://www.gnu.org/software/src-highlite -->
@@ -90,7 +90,7 @@ http://www.gnu.org/software/src-highlite -->
<p>In the above example, we can have two results. Either there was a line break in the buffer and we get it split into two parts, the line and the rest of the buffer; or there was no line break in the buffer and we need to get more data from the socket.</p>
<p>Next, we need to parse the line. The simplest way is to again split, here on space. The difference is that we want to split on all spaces character, as we want to tokenize the whole string.</p>
<div class="listingblock"><div class="title">Using binary:split/3 to split text</div>
-<div class="content"><!-- Generator: GNU source-highlight 3.1.8
+<div class="content"><!-- Generator: GNU source-highlight 3.1.9
by Lorenzo Bettini
http://www.lorenzobettini.it
http://www.gnu.org/software/src-highlite -->
@@ -111,7 +111,7 @@ http://www.gnu.org/software/src-highlite -->
<p>Sometimes the size of the frame includes the first four bytes, sometimes not. Other times this size is encoded over two bytes. And even other times little-endian is used instead of big-endian.</p>
<p>The general idea stays the same though.</p>
<div class="listingblock"><div class="title">Using binary pattern matching to split frames</div>
-<div class="content"><!-- Generator: GNU source-highlight 3.1.8
+<div class="content"><!-- Generator: GNU source-highlight 3.1.9
by Lorenzo Bettini
http://www.lorenzobettini.it
http://www.gnu.org/software/src-highlite -->