From c807880f7ac73f813b2660ea81a00f7712a4e793 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Lo=C3=AFc=20Hoguin?= Date: Mon, 29 Aug 2016 12:39:49 +0200 Subject: Add old mailing list archives --- .../archives/extend/2015-October/000557.html | 93 ++++++++++++++++++++++ 1 file changed, 93 insertions(+) create mode 100644 _build/static/archives/extend/2015-October/000557.html (limited to '_build/static/archives/extend/2015-October/000557.html') diff --git a/_build/static/archives/extend/2015-October/000557.html b/_build/static/archives/extend/2015-October/000557.html new file mode 100644 index 00000000..6d8fb533 --- /dev/null +++ b/_build/static/archives/extend/2015-October/000557.html @@ -0,0 +1,93 @@ + + + + [99s-extend] Cowboy: Maps instead of records for context variables + + + + + + + + + + +

[99s-extend] Cowboy: Maps instead of records for context variables

+ Ivan Uemlianin + ivan at llaisdy.com +
+ Tue Oct 20 15:19:05 CEST 2015 +

+
+ +
Dear All
+
+Would there be any reason against using a map instead of a record for 
+the context variable in a Cowboy REST resource?
+
+Quite often I have a few resources doing very similar things in their 
+callbacks, and I'd like to abstract out the similarities into a module - 
+but I don't want to share a record between modules.
+
+Maps seem to be a good fit, and I can't think of any downside 
+(performance hit should be tiny).
+
+Can anyone give me reasons to stick with records?
+
+With thanks and best wishes
+
+Ivan
+
+
+-- 
+============================================================
+Ivan A. Uemlianin PhD
+Llaisdy
+Speech Technology Research and Development
+
+                     ivan at llaisdy.com
+                         @llaisdy
+                          llaisdy.wordpress.com
+               github.com/llaisdy
+                      www.linkedin.com/in/ivanuemlianin
+
+                         festina lente
+============================================================
+
+
+ + + +
+

+ +
+More information about the Extend +mailing list
+ -- cgit v1.2.3