summaryrefslogtreecommitdiffstats
path: root/articles/page/3/index.html
diff options
context:
space:
mode:
Diffstat (limited to 'articles/page/3/index.html')
-rw-r--r--articles/page/3/index.html17
1 files changed, 17 insertions, 0 deletions
diff --git a/articles/page/3/index.html b/articles/page/3/index.html
index 8191ad8a..989deff6 100644
--- a/articles/page/3/index.html
+++ b/articles/page/3/index.html
@@ -67,6 +67,23 @@
<article class="blog_item">
<header>
+ <h2><a href="https://ninenines.eu/articles/cowboy2-qs/">Cowboy 2.0 and query strings</a></h2>
+ <p class="date">
+ <span class="year">2014</span>
+ <span class="day-month">20 Aug</span>
+ </p>
+ </header>
+
+ <p>Now that Cowboy 1.0 is out, I can spend some of my time thinking about Cowboy 2.0 that will be released soon after Erlang/OTP 18.0. This entry discusses the proposed changes to query string handling in Cowboy.
+Cowboy 2.0 will respond to user wishes by simplifying the interface of the cowboy_req module. Users want two things: less juggling with the Req variable, and more maps. Maps is the only dynamic key/value data structure in Erlang that we can match directly to extract values, allowing users to greatly simplify their code as they don&apos;t need to call functions to do everything anymore.</p>
+
+ <p style="text-align:right">
+ <a class="read_more" href="https://ninenines.eu/articles/cowboy2-qs/">Read More</a>
+ </p>
+ </article>
+
+ <article class="blog_item">
+ <header>
<h2><a href="https://ninenines.eu/articles/january-2014-status/">January 2014 status</a></h2>
<p class="date">
<span class="year">2014</span>