blob: 6d8fb53345fa4c68215c3261b955cb91baed7b51 (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<HTML>
<HEAD>
<TITLE> [99s-extend] Cowboy: Maps instead of records for context variables
</TITLE>
<LINK REL="Index" HREF="index.html" >
<LINK REL="made" HREF="mailto:extend%40lists.ninenines.eu?Subject=Re%3A%20%5B99s-extend%5D%20Cowboy%3A%20Maps%20instead%20of%20records%20for%20context%20variables&In-Reply-To=%3C56263F49.2000206%40llaisdy.com%3E">
<META NAME="robots" CONTENT="index,nofollow">
<style type="text/css">
pre {
white-space: pre-wrap; /* css-2.1, curent FF, Opera, Safari */
}
</style>
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
<LINK REL="Next" HREF="000558.html">
</HEAD>
<BODY BGCOLOR="#ffffff">
<H1>[99s-extend] Cowboy: Maps instead of records for context variables</H1>
<B>Ivan Uemlianin</B>
<A HREF="mailto:extend%40lists.ninenines.eu?Subject=Re%3A%20%5B99s-extend%5D%20Cowboy%3A%20Maps%20instead%20of%20records%20for%20context%20variables&In-Reply-To=%3C56263F49.2000206%40llaisdy.com%3E"
TITLE="[99s-extend] Cowboy: Maps instead of records for context variables">ivan at llaisdy.com
</A><BR>
<I>Tue Oct 20 15:19:05 CEST 2015</I>
<P><UL>
<LI>Next message: <A HREF="000558.html">[99s-extend] Cowboy: Maps instead of records for context variables
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#557">[ date ]</a>
<a href="thread.html#557">[ thread ]</a>
<a href="subject.html#557">[ subject ]</a>
<a href="author.html#557">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>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
<A HREF="https://lists.ninenines.eu/listinfo/extend">ivan at llaisdy.com</A>
@llaisdy
llaisdy.wordpress.com
github.com/llaisdy
www.linkedin.com/in/ivanuemlianin
festina lente
============================================================
</PRE>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI>Next message: <A HREF="000558.html">[99s-extend] Cowboy: Maps instead of records for context variables
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#557">[ date ]</a>
<a href="thread.html#557">[ thread ]</a>
<a href="subject.html#557">[ subject ]</a>
<a href="author.html#557">[ author ]</a>
</LI>
</UL>
<hr>
<a href="https://lists.ninenines.eu/listinfo/extend">More information about the Extend
mailing list</a><br>
</body></html>
|
