CODEWITHSUNDEEP
jsonjson-rpc
CQM
CQM

Reputation: 44258

Point of JSON-RPC vs simpler JSON

this is a JSON-RPC object I am implementing

{
         "method":"create",
         "params": [
                     {
                     "nid": "69",
                     "body": 
                                    {
                                    "und": 
                                        [
                                        {
                                        "value":
                                            "blah"
                                        }
                                        ]
                                    }   
                     }
                     ]
        }

here is how I would do it with "normal" JSON

 {
   "method":"create",
   "id":"69",
   "value":"blah"
 }

since JSON is a parsed as a map or dictionary, this should be adequate regardless of the presence of nested JSONArrays and JSON Objects in those arrays, explain why JSON-RPC is better or desired by anything at all

thanks!

Upvotes: 2

Views: 697

Answers (1)

Scott Hunter
Scott Hunter

Reputation: 49873

  • Your JSON-RPC is invalid; id has to be at the top level, as it is in your "normal" JSON
  • After correcting for the above, your JSON-RPC is still needlessly complex; params could just be [{"value":"blah"}]. Which would make your "normal" JSON very slightly less complex, but harder to parse (since you couldn't rely on "params" no matter what)
  • Your "normal" JSON would not allow for unnamed parameters (ones identified solely by position). Thus, the minimal added complexity buys you something which you might not need in your application, but others might

Upvotes: 1

Related Questions