diff options
| author | Loïc Hoguin <[email protected]> | 2019-07-18 09:59:28 +0200 |
|---|---|---|
| committer | Loïc Hoguin <[email protected]> | 2019-07-18 10:08:46 +0200 |
| commit | 136d443b5c38bee96f5d995dfea3629ef07564c3 (patch) | |
| tree | 1d31540baebc43ca0b2dceeda212c44f5da7e7a8 /articles/index.html | |
| parent | e031713c0e8bd871248dbbbbdec1ea28609f4431 (diff) | |
| download | ninenines.eu-136d443b5c38bee96f5d995dfea3629ef07564c3.tar.gz ninenines.eu-136d443b5c38bee96f5d995dfea3629ef07564c3.tar.bz2 ninenines.eu-136d443b5c38bee96f5d995dfea3629ef07564c3.zip | |
Announce Ranch 2.0.0-rc.1
Adds Ranch 2.0 documentation and removes documentation for
very old Cowboy and Ranch, along with Erlang.mk documentation
which is available on its own website.
Diffstat (limited to 'articles/index.html')
| -rw-r--r-- | articles/index.html | 35 |
1 files changed, 18 insertions, 17 deletions
diff --git a/articles/index.html b/articles/index.html index 005c857b..05b4ead7 100644 --- a/articles/index.html +++ b/articles/index.html @@ -67,6 +67,24 @@ <article class="blog_item"> <header> + <h2><a href="https://ninenines.eu/articles/ranch-2.0.0-rc.1/">Ranch 2.0 release candidate 1</a></h2> + <p class="date"> + <span class="year">2019</span> + <span class="day-month">18 Jul</span> + </p> + </header> + + <p>Ranch 2.0.0-rc.1 has been released! +We are getting very close to releasing Ranch 2.0! As most of the tremendous programming work was done by contributor Jan Uhlig, I will yield the floor and let him describe what went into this great release. +In Ranch 1.x, there is only one supervisor per Ranch listener to start and manage connection processes. Under high load (many clients rapidly connecting and/or disconnecting), the message queue of this one supervisor could becomes congested, leading to declining accept rates or a stalled listener.</p> + + <p style="text-align:right"> + <a class="read_more" href="https://ninenines.eu/articles/ranch-2.0.0-rc.1/">Read More</a> + </p> + </article> + + <article class="blog_item"> + <header> <h2><a href="https://ninenines.eu/articles/joe_the_rubber_duck/">Joe Armstrong the rubber duck</a></h2> <p class="date"> <span class="year">2019</span> @@ -419,23 +437,6 @@ You lost them. You know you lost them. They comment on the syntax, or perhaps yo </p> </article> - <article class="blog_item"> - <header> - <h2><a href="https://ninenines.eu/articles/dont-let-it-crash/">Don't let it crash</a></h2> - <p class="date"> - <span class="year">2017</span> - <span class="day-month">22 Jan</span> - </p> - </header> - - <p>We have a specific mindset when writing Erlang programs. We focus on the normal execution of the program and don't handle most of the errors that may occur. We sometimes call this normal execution the happy path. -The general pattern behind writing only for the happy path, letting the VM catch errors (writing them to a log for future consumption) and then having a supervisor restart the processes that failed from a clean state, has a name.</p> - - <p style="text-align:right"> - <a class="read_more" href="https://ninenines.eu/articles/dont-let-it-crash/">Read More</a> - </p> - </article> - <nav class="pagination" role="pagination"> |