summaryrefslogtreecommitdiff
path: root/res/ari
diff options
context:
space:
mode:
authorDavid M. Lee <dlee@digium.com>2013-08-02 14:27:35 +0000
committerDavid M. Lee <dlee@digium.com>2013-08-02 14:27:35 +0000
commit10c91bc96eafbf5f897869ede83127c9c267981c (patch)
treec9aaaf3cc4c9794057e258166854d5f88a6a0c18 /res/ari
parent328e99f41d48d8f15832bf4f6c97beb0ef71fc0c (diff)
Address JSON thread safety issues.
In tracking down some unit tests failures, I ended up reading the fine print[1] regarding Jansson's thread safety. In short: 1. Ref-counting is non-atomic. 2. json_dumps() and friends are not thread safe. This patch adds locking where necessary to our ast_json_* wrapper API, with documentation in json.h describing the thread safety limitations of the API. [1]: http://www.digip.org/jansson/doc/2.4/portability.html#thread-safety Review: https://reviewboard.asterisk.org/r/2716/ git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@396119 65c4cc65-6c06-0410-ace0-fbb531ad65f3
Diffstat (limited to 'res/ari')
-rw-r--r--res/ari/ari_websockets.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/res/ari/ari_websockets.c b/res/ari/ari_websockets.c
index 13650c293..a34e0f691 100644
--- a/res/ari/ari_websockets.c
+++ b/res/ari/ari_websockets.c
@@ -142,7 +142,7 @@ struct ast_json *ast_ari_websocket_session_read(
int ast_ari_websocket_session_write(struct ast_ari_websocket_session *session,
struct ast_json *message)
{
- RAII_VAR(char *, str, NULL, ast_free);
+ RAII_VAR(char *, str, NULL, ast_json_free);
#ifdef AST_DEVMODE
if (!session->validator(message)) {