[asterisk-bugs] [Asterisk 0014281]: [patch] JSON Manager Event Interface

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=14281 
====================================================================== 
Reported By:                PLL
Assigned To:                dbrooks
====================================================================== 
Project:                    Asterisk
Issue ID:                   14281
Category:                   Core/ManagerInterface/NewFeature
Reproducibility:            N/A
Severity:                   feature
Priority:                   normal
Status:                     feedback
Asterisk Version:           SVN 
Regression:                 No 
SVN Branch (only for SVN checkouts, not tarball releases):  trunk 
SVN Revision (number only!): 169443 
Request Review:              
====================================================================== 
Date Submitted:             2009-01-19 20:02 CST
Last Modified:              2009-05-28 00:22 CDT
====================================================================== 
Summary:                    [patch] JSON Manager Event Interface
Description: 
Make it easier to work with pure javascript Asterisk managers. Just adding
another option.
====================================================================== 

---------------------------------------------------------------------- 
 (0105606) PLL (reporter) - 2009-05-28 00:22
 https://issues.asterisk.org/view.php?id=14281#c105606 
---------------------------------------------------------------------- 
Valid json strings are between ""

A json object is made of { string : value }

This works because it's valid javascript:
{a_name:"a value"}

This is valid json:
{"a_name":"a value"}

They are both the same javascript object, but the later has a couple extra
characters, seems like a waste but...

What about this case?
{a name:"a value"}

The above will fail, it's not properly formatted. The correct format is:
{"a name":"a value"}

Another problem when not using proper json strings for labels is:
{case:"a value"}

Once again, the above will fail. case is part of the javascript language
so it's a restricted keyword but this works as expected:
{"case":"a value"}

With valid json labels I can even put atypical labels:
{" 12 ":"a value"}

It's desirable to have valid json labels. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-05-28 00:22 PLL            Note Added: 0105606                          
======================================================================